Method and apparatus for performing sensing procedure in wireless LAN system

Abstract

A method and an apparatus performed in a wireless LAN system are disclosed. According to one embodiment of the present disclosure, a method performed by means of a first STA in a wireless LAN system comprises the steps of: receiving, from a second STA, a sensing trigger frame including a sensing trigger subtype field, the sensing trigger subtype field including information indicating that the sensing trigger frame is an SR2SR probe trigger frame; and transmitting an SR2SR NDP to at least one STA or receiving the SR2SR NDP from the at least one STA based on the sensing trigger frame in the SR2SR sounding step, in which the sensing trigger frame may include information indicating a role of the first STA in the SR2SR sounding step.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for performing communication in a wireless local area network (WLAN) system, and more particularly, to a method and apparatus for performing sensing measurement in a next generation wireless LAN system. Background Art

[0002] New technologies have been introduced for wireless LAN (WLAN) to increase transmission rates, increase bandwidth, improve reliability, reduce errors, and reduce latency. Among WLAN technologies, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards may be referred to as Wi-Fi. For example, technologies recently introduced to WLAN include the Very High Throughput (VHT) enhancements of the 802.11ac standard and the High Efficiency (HE) enhancements of the IEEE 802.11ax standard.

[0003] Improved technologies for providing sensing for devices using wireless LAN signals are being discussed. For example, in the IEEE 802.11 Task Group (TG) bf, standard technologies for sensing objects (e.g., people, objects, etc.) based on channel estimation using wireless LAN signals between devices operating in frequency bands below 7 GHz are being developed. Object sensing based on wireless LAN signals has the advantage of utilizing existing frequency bands and is less likely to infringe on privacy than existing sensing technologies. As the frequency range used in wireless LAN technology increases, accurate sensing information can be obtained, and technologies that reduce power consumption to effectively support accurate sensing processes are being studied. Summary of the invention

[0004] Technical issues

[0005] The technical problem of the present disclosure is to provide a method and an apparatus for performing a sensing process in a wireless LAN system.

[0006] An additional technical problem of the present disclosure is to provide a method and apparatus for performing a Sensing Responder to Sensing Responder (SR2SR) measurement procedure.

[0007] An additional technical problem of the present disclosure is to provide a method and apparatus for indicating the role of a sensing responder in a SR2SR probing phase.

[0008] The technical objectives to be achieved by the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the art can clearly understand other technical objectives not described herein through the following description.

[0009] Technical Solution

[0010] According to one embodiment of the present disclosure, a method performed by a first station (STA) in a wireless LAN system may include: receiving a sensing trigger frame including a sensing trigger subtype field from a second STA, wherein the sensing trigger subtype field includes information indicating that the sensing trigger frame is an SR2SR (sensing responder to sensing responder) detection trigger frame; and sending an SR2SR NDP (Null Data Physical Protocol Data Unit (PPDU)) to at least one STA based on the sensing trigger frame in the SR2SR detection phase or receiving the SR2SR NDP from the at least one STA, wherein the sensing trigger frame may include information indicating the role of the first STA in the SR2SR detection phase.

[0011] According to one embodiment of the present disclosure, a method performed by a second station (STA) in a wireless LAN system may include: sending a sensing trigger frame including a sensing trigger subtype field to multiple STAs including a first STA; and receiving, from at least one STA among the multiple STAs in an SR2SR (sensing responder to sensing responder) detection phase, a measurement result based on an SR2SR NDP (Null Data Physical Protocol Data Unit (PPDU)) sent by the sensing trigger frame, and the sensing trigger frame may include information indicating a role of the first STA in the SR2SR detection phase.

[0012] Technical Effects

[0013] According to the present disclosure, a method and an apparatus for performing a sensing process in a wireless LAN system may be provided.

[0014] According to various embodiments of the present disclosure, a method and apparatus for performing an SR2SR measurement process may be provided.

[0015] According to various embodiments of the present disclosure, a method and apparatus for indicating the role of a sensing responder in an SR2SR probing phase may be provided, thereby improving the accuracy of sensing measurements.

[0016] Effects achievable by the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those skilled in the art through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to understand the present disclosure, the accompanying drawings, which are included as a part of the detailed description, provide embodiments of the present disclosure and describe technical features of the present disclosure in detail.

[0018] Figure 1 A configuration block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0019] Figure 2 is a diagram illustrating an exemplary structure of a WLAN system to which the present disclosure can be applied.

[0020] Figure 3 is a diagram for describing a link establishment process to which the present disclosure can be applied.

[0021] Figure 4 is a diagram for describing a backoff process to which the present disclosure can be applied.

[0022] Figure 5 is a diagram for describing a CSMA / CA-based frame transmission operation to which the present disclosure may be applied.

[0023] Figure 6 is a diagram for describing an example of a frame structure used in a WLAN system to which the present disclosure can be applied.

[0024] Figure 7 is a diagram illustrating an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0025] Figures 8 to 10 is a diagram for describing an example of a resource unit of a WLAN system to which the present disclosure can be applied.

[0026] Fig.11 An example structure of the HE-SIG-B field is illustrated.

[0027] Fig.12 is a diagram for describing a MU-MIMO method in which multiple users / STAs are assigned to one RU.

[0028] Fig.13 An example of a PPDU format to which the present disclosure can be applied is illustrated.

[0029] Fig.14 An example format of a trigger frame to which the present disclosure may be applied is illustrated.

[0030] Fig.15 is a diagram for describing a HE non-TB / TB detection process to which the present disclosure may be applied.

[0031] Fig.16 is a diagram for describing a process in which a first STA performs a sensing process according to an embodiment of the present disclosure.

[0032] Fig.17 is a diagram for describing a process in which a second STA performs a sensing process according to an embodiment of the present disclosure.

[0033] Fig.18is a diagram for describing a process of performing an SBP procedure according to an embodiment of the present disclosure.

[0034] Fig.19 , Fig. 20 and Fig.21 is a diagram for describing a method of performing an SR2SR measurement process according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed by the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, rather than to represent the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art know that the present disclosure can be implemented without these specific details.

[0036] In some cases, well-known structures and devices may be omitted, or may be shown in the form of a block diagram based on the core functions of each structure and device in order to prevent ambiguity of the concepts of the present disclosure.

[0037] In the present disclosure, when an element is referred to as being "connected", "combined" or "linked" to another element, it may include an indirect connection relationship between which another element exists as well as a direct connection relationship. In addition, in the present disclosure, the term "comprising" or "having" specifies the presence of the mentioned features, steps, operations, components and / or elements, but does not exclude the presence or addition of one or more other features, stages, operations, components, elements and / or groups thereof.

[0038] In the present disclosure, terms such as "first", "second", etc. are only used to distinguish one element from another element and are not used to limit the elements, and unless otherwise specified, they do not limit the order or importance between elements, etc. Therefore, within the scope of the present disclosure, the first element in an embodiment may be referred to as the second element in another embodiment, and similarly, the second element in an embodiment may be referred to as the first element in another embodiment.

[0039] The terms used in this disclosure are intended to describe specific embodiments, rather than to limit the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form, unless the context clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the related enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise stated, the " / " between words in the present invention has the same meaning as "and / or".

[0040] Examples of the present disclosure can be applied to various wireless communication systems. For example, examples of the present disclosure can be applied to wireless LAN systems. For example, examples of the present disclosure can be applied to wireless LANs based on IEEE 802.11a / g / n / ac / ax standards. In addition, examples of the present disclosure can be applied to wireless LANs based on the newly proposed IEEE 802.11be (or EHT) standard. Examples of the present disclosure can be applied to wireless LANs based on the IEEE802.11be version 2 standard corresponding to the additional enhanced technology of the IEEE 802.11be version 1 standard. In addition, examples of the present disclosure can be applied to wireless LANs based on next-generation standards after IEEE 802.11be. In addition, examples of the present disclosure can be applied to cellular wireless communication systems. For example, it can be applied to cellular wireless communication systems based on long term evolution (LTE) technology and 5G new radio (NR) technology based on the third generation partnership project (3GPP) standard.

[0041] Hereinafter, technical features of examples to which the present disclosure can be applied will be described.

[0042] Figure 1 A block diagram of a wireless communication device according to an embodiment of the present disclosure is illustrated.

[0043] Figure 1 The first device 100 and the second device 200 illustrated in the figure may be replaced with various terms such as terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), mobile subscriber unit (MSU), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT) or simple user, etc. In addition, the first device 100 and the second device 200 include an access point (AP), a base station (BS), a fixed station, a node B, a base transceiver system (BTS), a network. It may be replaced with various terms such as an artificial intelligence (AI) system, a roadside unit (RSU), a repeater, a router, a relay and a gateway.

[0044] Figure 1 The devices 100 and 200 illustrated in the example may be referred to as stations (STAs). Figure 1The devices 100 and 200 illustrated in the figure may be referred to by various terms such as a transmitting device, a receiving device, a transmitting STA, and a receiving STA. For example, the STAs 110 and 200 may perform an access point (AP) role or a non-AP role. That is, in the present disclosure, the STAs 110 and 200 may perform the functions of an AP and / or a non-AP. When the STAs 110 and 200 perform the AP function, they may be simply referred to as APs, and when the STAs 110 and 200 perform the non-AP function, they may be simply referred to as STAs. In addition, in the present disclosure, an AP may also be indicated as an AP STA.

[0045] refer to Figure 1 , the first device 100 and the second device 200 can send and receive radio signals through various wireless LAN technologies (e.g., IEEE802.11 series). The first device 100 and the second device 200 may include interfaces for a media access control (MAC) layer and a physical layer (PHY) that conform to the IEEE802.11 standard.

[0046] In addition, in addition to the wireless LAN technology, the first device 100 and the second device 200 may further support various communication standards (e.g., 3GPP LTE series, 5G NR series standards, etc.) technologies. In addition, the device of the present disclosure may be implemented in various devices such as mobile phones, vehicles, personal computers, augmented reality (AR) devices, and virtual reality (VR) devices. In addition, the STA of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, machine type communications (MTC), machine to machine (M2M), device to device (D2D), IoT (Internet of Things), etc.

[0047] The first device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. For example, the processor 102 may send a wireless signal including the first information / signal through the transceiver 106 after generating the first information / signal by processing the information in the memory 104. In addition, the processor 102 may receive a wireless signal including the second information / signal through the transceiver 106, and then store the information obtained by the signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including instructions for executing all or part of the processing controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., IEEE 802.11 series). The transceiver 106 may be connected to the processor 102 and may send and / or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a device may refer to a communication modem / circuit / chip.

[0048] The second device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in the present disclosure. For example, the processor 202 may generate third information / signals by processing the information in the memory 204, and then send a wireless signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signals through the transceiver 206, and then store information obtained by signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing all or part of the processing controlled by the processor 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts included in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless LAN technology (e.g., IEEE 802.11 series). The transceiver 206 may be connected to the processor 202 and may send and / or receive wireless signals through one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a device may refer to a communication modem / circuit / chip.

[0049] In the following, the hardware elements of the apparatus 100, 200 will be described in more detail. Without limitation thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the description, function, process, suggestion, method, and / or operation flow chart disclosed in the present disclosure. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, suggestions, and / or methods disclosed in the present disclosure to provide them to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 according to the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure and obtain a PDU, SDU, message, control information, data, or information.

[0050] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, and the like. Firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operational flow charts included in the present disclosure may be implemented using firmware or software in the form of codes, instructions and / or instruction sets.

[0051] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0052] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the method and / or operation flow chart of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the description, function, process, suggestion, method and / or operation flow chart, etc. included in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may send and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to send and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, suggestions, methods and / or operation flow charts, etc. included in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals into baseband signals to process received user data, control information, wireless signals / channels, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals into RF band signals. Thus, one or more of the transceivers 106 , 206 may include (analog) oscillators and / or filters.

[0053] For example, one of the STAs 100 and 200 may perform the expected operation of an AP, and the other of the STAs 100 and 200 may perform the expected operation of a non-AP STA. Figure 1 The transceivers 106 and 206 of the present invention may perform transmission and reception operations of signals (e.g., packets or physical layer protocol data units (PPDUs) compliant with IEEE 802.11a / b / g / n / ac / ax / be). In addition, in the present disclosure, operations of various STAs generating transmission / reception signals or performing data processing or calculations on transmission / reception signals in advance may be performed by Figure 1The processors 102 and 202 are executed. For example, examples of operations of generating a transmission / reception signal or performing data processing or calculation for the transmission / reception signal in advance may include: 1) determining / obtaining / configuring / calculating / decoding / encoding bit information of fields (signal (SIG), short training field (STF), long training field (LTF), data, etc.) included in the PPDU; 2) determining / configuring / obtaining time resources or frequency resources (e.g., subcarrier resources) for fields (SIG, STF, LTF, data, etc.) included in the PPDU; 3) determining / configuring / obtaining a specific sequence (e.g., pilot sequence, STF / LTF sequence, additional sequence applied to SIG) for fields (SIG, STF, LTF, data, etc.) included in the PPDU action; 4) power control operations and / or power saving operations applied to STAs; 5) operations related to ACK signal determination / obtaining / configuring / calculating / decoding / encoding, etc. In addition, in the following example, various information used by various STAs to determine / acquire / configure / calculate / decode / encode transmission signals and reception signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) may be stored in Figure 1 in the memories 104 and 204.

[0054] Hereinafter, a downlink (DL) may mean a link for communication from an AP STA to a non-AP STA, and a DL PPDU / packet / signal may be transmitted and received through the DL. In DL communication, a transmitter may be a part of an AP STA, and a receiver may be a part of a non-AP STA. An uplink (UL) may mean a link for communication from a non-AP STA to an AP STA, and a UL PPDU / packet / signal may be transmitted and received through the UL. In UL communication, a transmitter may be a part of a non-AP STA, and a receiver may be a part of an AP STA.

[0055] Figure 2 is a diagram illustrating an exemplary structure of a wireless LAN system to which the present disclosure can be applied.

[0056] The structure of the wireless LAN system may be composed of a plurality of components. A wireless LAN supporting STA mobility transparent to an upper layer may be provided through the interaction of the plurality of components. A basic service set (BSS) corresponds to a basic building block of a wireless LAN. Figure 2 It is exemplarily shown that two BSSs (BSS1 and BSS2) exist, and two STAs (STA1 and STA2 are included in BSS1, and STA3 and STA4 are included in BSS2) are included as members of each BSS. Figure 2The ellipse representing the BSS in the figure can also be understood as representing the coverage area in which the STAs included in the corresponding BSS maintain communication. This area can be called a basic service area (BSA). When a STA moves outside the BSA, it cannot communicate directly with other STAs in the BSA.

[0057] If you don't consider Figure 2 , the most basic BSS type in the wireless LAN is an independent BSS (IBSS), if the DS is shown in FIG. 1 . For example, an IBSS may have a minimum form containing only two STAs. For example, assuming that other components are omitted, a BSS1 containing only STA1 and STA2 or a BSS2 containing only STA3 and STA4 may correspond to representative examples of IBSSs, respectively. This configuration is possible when STAs can communicate directly without an AP. In addition, in this type of wireless LAN, it is not pre-configured but can be configured when a LAN is needed, and this may be referred to as an ad-hoc network. Since the IBSS does not include an AP, there is no centralized management entity. That is, in the IBSS, STAs are managed in a distributed manner. In an IBSS, all STAs may be composed of mobile STAs, and access to a distributed system (DS) is not allowed, thereby forming a self-contained network.

[0058] The membership of a STA in a BSS can be changed dynamically by turning the STA on or off, entering or exiting a BSS region, etc. In order to become a member of a BSS, a STA can join the BSS using a synchronization process. In order to access all services of the BSS infrastructure, a STA should associate with the BSS. This association can be established dynamically and can include the use of a distributed system service (DSS).

[0059] The direct STA-to-STA distance in a wireless LAN may be limited by PHY performance. In some cases, this distance limitation may be sufficient, but in some cases, communication between STAs at longer distances may be required. A distributed system (DS) can be configured to support extended coverage.

[0060] DS refers to the structure of BSS interconnection. Specifically, Figure 2As shown, the BSS can exist as an extended form of a network composed of multiple BSSs. DS is a logical concept and can be specified by the characteristics of the distributed system medium (DSM). At this point, the wireless medium (WM) and the DSM can be logically separated. Each logical medium is used for different purposes and is used by different components. These media are not limited to being the same, nor are they limited to being different. In this way, the flexibility of the wireless LAN structure (DS structure or other network structure) can be interpreted as multiple media being logically different. That is, the wireless LAN structure can be implemented in various ways, and the corresponding wireless LAN structure can be independently specified by the physical characteristics of each implementation.

[0061] DS can support mobile devices by providing seamless integration of multiple BSSs and providing logical services necessary to address the address leading to the destination. In addition, DS can also include a component called a portal, which is used as a bridge for connection between wireless LAN and other networks (e.g., IEEE 802.X).

[0062] The AP enables access to the DS through the WM for associated non-AP STAs and means an entity that also has STA functionality. Data movement between the BSS and the DS can be performed through the AP. For example, Figure 2 STA2 and STA3 shown in the figure have the function of STA and provide the function of allowing the associated non-AP STA (STA1 and STA4) to access the DS. In addition, since all APs basically correspond to STAs, all APs are addressable entities. The address used by the AP to communicate on the WM is not necessarily the same as the address used by the AP to communicate on the DSM. A BSS composed of an AP and one or more STAs may be referred to as an infrastructure BSS.

[0063] Data sent from one of the STAs associated with the AP to the STA address of the corresponding AP can always be received at the uncontrolled port and can be processed by the IEEE 802.1X port access entity. In addition, when the controlled port is authenticated, the transmitted data (or frame) can be delivered to the DS.

[0064] In addition to the above-mentioned structure of the DS, an extended service set (ESS) may also be configured to provide wide coverage.

[0065] ESS means a network with arbitrary size and complexity consisting of DS and BSS. ESS may correspond to a set of BSSs connected to one DS. However, ESS does not include DS. The ESS network is characterized by being regarded as an IBSS in the logical link control (LLC) layer. The STAs included in the ESS can communicate with each other, and the mobile STA can move from one BSS to another (within the same ESS) transparently for LLC. The APs included in one ESS may have the same service set identifier (SSID). SSID is distinguished from BSSID, which is an identifier of BSS.

[0066] The wireless LAN system does not assume anything about the relative physical location of the BSS, and all of the following forms are possible. The BSS may partially overlap, which is a form commonly used to provide continuous coverage. In addition, the BSS may not be physically connected, and logically, there is no limit on the distance between the BSS. In addition, the BSS may be physically located in the same location, which can be used to provide redundancy. In addition, one (or more than one) IBSS or ESS network may physically exist in the same space as one (or more than one) ESS network. When an ad hoc network operates in a location where an ESS network exists, when physically overlapping wireless networks are configured by different organizations, or when two or more different access and security policies are required in the same location, this may correspond to the form of an ESS network, etc.

[0067] Figure 3 is a diagram for explaining a link establishment process to which the present disclosure can be applied.

[0068] In order for a STA to establish a link with respect to a network and send / receive data, it first discovers the network, performs authentication, establishes association, and needs to perform authentication processing for security. The link establishment processing may also be referred to as a session initiation processing or a session establishment processing. In addition, the processes of discovery, authentication, association, and security setting of the link establishment processing may be collectively referred to as an association processing.

[0069] In step S310, the STA may perform a network discovery operation. The network discovery operation may include a scanning operation of the STA. That is, in order for the STA to access a network, it needs to find a network that it can participate in. The STA should identify compatible networks before participating in a wireless network, and the process of identifying networks present in a specific area is called scanning.

[0070] Scanning schemes include active scanning and passive scanning. Figure 3The network discovery operation including active scanning processing is exemplarily illustrated. In active scanning, the STA performing the scan sends a probe request frame to discover which APs exist around it while the channel moves and waits for a response thereto. The responder sends a probe response frame as a response to the probe request frame to the STA that has sent the probe request frame. Here, the responder may be the STA that last sent a beacon frame in the BSS of the channel being scanned. In the BSS, since the AP sends a beacon frame, the AP becomes the responder, and in the IBSS, the STAs in the IBSS rotate to send beacon frames, so the responder is not constant. For example, a STA that sends a probe request frame on channel 1 and receives a probe response frame on channel 1 may store the BSS-related information included in the received probe response frame, and may move to the next channel (e.g., channel 2), and perform scanning in the same manner (i.e., sending and receiving probe requests / responses on channel 2).

[0071] Although not in Figure 3 , but the scanning operation can be performed in a passive scanning manner. In passive scanning, the STA performing the scan waits for a beacon frame while the channel moves. The beacon frame is one of the management frames defined in IEEE 802.11, and is periodically sent to notify the existence of a wireless network and allow the STA performing the scan to find the wireless network and participate in the wireless network. In the BSS, the AP is used to periodically send beacon frames, and in the IBSS, the STAs within the IBSS rotate to send beacon frames. When the STA performing the scan receives the beacon frame, the STA stores the information of the BSS included in the beacon frame, and records the beacon frame information in each channel while moving to another channel. The STA receiving the beacon frame can store the BSS-related information included in the received beacon frame, move to the next channel, and perform scanning in the next channel in the same manner. Comparing active scanning with passive scanning, the advantage of active scanning is that it has less delay and less power consumption than passive scanning.

[0072] After the STA discovers the network, an authentication process may be performed at step S320. In order to clearly distinguish from the security establishment operation of step S340 to be described later, this authentication process may be referred to as a first authentication process.

[0073] The authentication process includes the following process: the STA sends an authentication request frame to the AP, and in response thereto, the AP sends an authentication response frame to the STA. The authentication frame for authentication request / response corresponds to a management frame.

[0074] The authentication frame includes an authentication algorithm number, an authentication transaction sequence number, a status code, a challenge text, a robust security network (RSN), a limited cycle group, etc. This corresponds to some examples of information that can be included in the authentication request / response frame, and can be replaced with other information, or additional information can also be included.

[0075] The STA may send an authentication request frame to the AP. The AP may determine whether to allow authentication of the corresponding STA based on the information included in the received authentication request frame. The AP may provide the result of the authentication process to the STA via an authentication response frame.

[0076] After the STA is successfully authenticated, an association process may be performed at step S330. The association process includes the following processes: the STA sends an association request frame to the AP, and in response, the AP sends an association response frame to the STA.

[0077] For example, the association request frame may include information related to various capabilities, a beacon listening interval, a service set identifier (SSID), supported rates, supported channels, RSN, a mobile domain, supported operation categories, a traffic indication map broadcast request (TIM broadcast request), interworking service capabilities, etc. For example, the association response frame may include information related to various capabilities, a status code, an association ID (AID), supported rates, an enhanced distributed channel access (EDCA) parameter set, a received channel power indicator (RCPI), a received signal-to-noise ratio indicator (RSNI), a mobile domain, a timeout interval (e.g., an association recovery time), an overlapping BSS scanning parameter, a TIM broadcast response, a quality of service (QoS) map, etc. This corresponds to some examples of information that may be included in an association request / response frame, and may be replaced with other information, or may also include additional information.

[0078] After the STA successfully associates with the network, a security establishment process may be performed at step S340. The security establishment process at step S340 may be referred to as an authentication process through a robust security network association (RSNA) request / response, the authentication process at step S320 may be referred to as a first authentication process, and the security establishment process at step S340 may also be referred to simply as an authentication process.

[0079] The security establishment process of step S340 may include, for example, a process of setting a private key through an Extensible Authentication Protocol over LAN (EAPOL) frame using a four-way handshake. In addition, the security establishment process may be performed according to a security scheme not defined in the IEEE 802.11 standard.

[0080] Figure 4 It is a diagram for explaining a backoff process to which the present disclosure can be applied.

[0081] In a wireless LAN system, the basic access mechanism of the medium access control (MAC) is a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism is also known as the distributed coordination function (DCF) of the IEEE 802.11 MAC, and basically adopts a "listen before talk" access mechanism. According to this type of access mechanism, before starting to send, the AP and / or STA may perform a clear channel assessment (CCA) of sensing the radio channel or medium during a predetermined time interval (e.g., DCF interframe space (DIFS)). As a result of the sensing, if it is determined that the medium is in an idle state, frame transmission is started through the corresponding medium. On the other hand, if it is detected that the medium is occupied or busy, the corresponding AP and / or STA does not start its own transmission, and a delay period (e.g., a random backoff period) for medium access may be set and frame transmission may be attempted after waiting. By applying a random backoff period, since multiple STAs are expected to attempt frame transmission after waiting for different time periods, conflicts can be minimized.

[0082] In addition, the IEEE 802.11 MAC protocol provides a hybrid coordination function (HCF). HCF is based on DCF and point coordination function (PCF). PCF is a synchronous access method based on polling, and refers to a method in which all receiving APs and / or STAs periodically poll to receive data frames. In addition, HCF has enhanced distributed channel access (EDCA) and HCF controlled channel access (HCCA). EDCA is a contention-based access method that provides data frames to multiple users in a direction, and HCCA uses a non-contention-based channel access method that utilizes a polling mechanism. In addition, HCF includes a medium access mechanism for improving the QoS (quality of service) of a wireless LAN, and QoS data can be sent during a contention period (CP) and a contention-free period (CFP).

[0083] refer to Figure 4 , the operation based on the random backoff period will be described. When the occupied / busy medium becomes idle, multiple STAs can attempt to send data (or frames). As a method to minimize conflicts, each of the STAs can select a random backoff count respectively and attempt to send after waiting for the corresponding time slot time. The random backoff count has a pseudo-random integer value and can be determined as one of the values ​​ranging from 0 to CW. Here, CW is the contention window parameter value. The CW parameter is assigned CWmin as an initial value, but can take a value twice as large in the event of a transmission failure (for example, when an ACK for the transmitted frame is not received). When the CW parameter value reaches CWmax, data transmission can be attempted while maintaining the CWmax value until the data transmission is successful, and when the data transmission is successful, the CWmin value is reset. The values ​​of CW, CWmin and CWmax are preferably set to 2.n -1(n=0, 1, 2, . . . ).

[0084] When the random backoff process starts, the STA continuously monitors the medium in the backoff slot countdown according to the determined backoff count value. When the medium is monitored for occupancy, it stops the countdown and waits, and restarts the remaining part of the countdown when the medium becomes idle.

[0085] exist Figure 4 In the example of , when the packet to be sent arrives at the MAC of STA 3, STA3 can send the frame immediately after confirming that the medium has been idle for up to DIFS. The remaining STAs monitor and wait for the medium to be occupied / busy. At the same time, the data to be sent can also occur in each of STA1, STA2 and STA5, and when the medium is monitored as idle, each STA waits for up to DIFS, and then the countdown of the backoff slot can be performed according to the random backoff count value selected by each STA. Assume that STA2 selects the minimum backoff count value and STA1 selects the maximum backoff count value. That is, the example illustrates the case where the remaining backoff time of STA5 is shorter than the remaining backoff time of STA1 when STA2 completes the backoff count and starts frame transmission. STA1 and STA5 temporarily stop the countdown and wait when STA2 occupies the medium. When STA2's occupation ends and the medium becomes idle again, STA1 and STA5 wait for DIFS and restart the stopped backoff count. That is, frame transmission can start after counting down the remaining backoff slot for the remaining backoff time. Since the remaining backoff time of STA5 is shorter than that of STA1, STA5 starts frame transmission. The data to be transmitted may also occur in STA4 while STA2 occupies the medium. From the perspective of STA4, when the medium becomes idle, STA4 may wait for DIFS, and then may perform a countdown according to a random backoff count value selected by STA4, and start transmitting frames. Figure 4 The example shows a case where the remaining backoff time of STA5 accidentally collides with the random backoff count value of STA4. In this case, a collision may occur between STA4 and STA5. When a collision occurs, neither STA4 nor STA5 receives an ACK, so data transmission fails. In this case, STA4 and STA5 can double the CW value, select a random backoff count value, and perform a countdown. While the medium is occupied due to the transmission of STA4 and STA5, STA1 waits, and when the medium becomes idle, STA1 waits DIFS, and then starts frame transmission after the remaining backoff time has passed.

[0086] As in Figure 4In the example of , a data frame is a frame for sending data forwarded to a higher layer, and may be sent after a backoff performed after DIFS has passed since the medium became idle. In addition, a management frame is a frame for exchanging management information that is not forwarded to a higher layer, and is sent after a backoff is performed after an IFS such as DIFS or a point coordination function IFS (PIFS). As subtype frames of the management frame, there are beacons, association requests / responses, reassociation requests / responses, probe requests / responses, authentication requests / responses, and the like. A control frame is a frame for controlling access to a medium. As subtype frames of the control frame, there are request to send (RTS), clear to send (CTS), acknowledgement (ACK), power save poll (PS-Poll), block ACK (BlockAck), block ACK request (BlockACKReq), empty data packet announcement (NDP announcement), and trigger, and the like. If the control frame is not a response frame of the previous frame, it is sent after performing a backoff after DIFS has passed, and if it is a response frame of the previous frame, it is sent without performing a backoff after a short IFS (SIFS) has passed. The type and subtype of the frame can be identified by the type field and subtype field in the frame control (FC) field.

[0087] Quality of Service (QoS) STA can perform a backoff performed after arbitration IFS (AIFS) (i.e., AIFS [i] (where i is a value determined by AC)) for the access category (AC) to which the frame belongs, and then can send the frame. Here, the frame that can use AIFS [i] may be a data frame, a management frame, or a control frame instead of a response frame.

[0088] Figure 5 is a diagram for explaining a frame transmission operation based on CSMA / CA to which the present disclosure can be applied.

[0089] As described above, in addition to the physical carrier sensing in which the STA directly senses the medium, the CSMA / CA mechanism also includes virtual carrier sensing. Virtual carrier sensing is intended to compensate for problems such as hidden node problems that may occur in medium access. For virtual carrier sensing, the MAC of the STA can use a network allocation vector (NAV). NAV is a value that indicates to other STAs the remaining time until the medium is available for use by the STA that is currently using or has the right to use the medium. Therefore, the value set to NAV corresponds to the period during which the STA sending the frame plans to use the medium, and during the corresponding period, the STA receiving the NAV value is prohibited from accessing the medium. For example, the NAV can be configured based on the value of the "Duration" field of the MAC header of the frame.

[0090] exist Figure 5In the example of FIG. 1 , it is assumed that STA1 intends to send data to STA2, and STA3 is in a position to be able to eavesdrop on some or all frames sent and received between STA1 and STA2.

[0091] In order to reduce the possibility of transmission conflicts among multiple STAs in the frame transmission operation based on CSMA / CA, a mechanism using RTS / CTS frames can be applied. Figure 5 In the example of , when STA1's transmission is being performed, as a result of STA3's carrier sensing, it can be determined that the medium is in an idle state. That is, STA1 may correspond to a hidden node with respect to STA3. Alternatively, in Figure 5 In the example of , it can be determined that the carrier sensing result medium of STA3 is in an idle state while the transmission of STA2 is being performed. That is, STA2 may correspond to a hidden node with respect to STA3. By exchanging RTS / CTS frames before performing data transmission and reception between STA1 and STA2, STAs outside the transmission range of one of STA1 or STA2 or STAs outside the carrier sensing range of the transmission from STA1 or STA3 may not attempt to occupy the channel during data transmission and reception between STA1 and STA2.

[0092] Specifically, STA1 can determine whether the channel is being used by carrier sensing. In terms of physical carrier sensing, STA1 can determine the channel occupancy idle state based on the energy level or signal correlation detected in the channel. In addition, in terms of virtual carrier sensing, STA1 can use the network allocation vector (NAV) timer to determine the channel occupancy state.

[0093] When the channel is in an idle state during DIFS, STA1 may send an RTS frame to STA2 after performing backoff. When STA2 receives the RTS frame, STA2 may send a CTS frame to STA1 as a response to the RTS frame after SIFS.

[0094] If STA3 cannot eavesdrop on the CTS frame from STA2 but can eavesdrop on the RTS frame from STA1, STA3 can set the NAV timer for the frame transmission period (e.g., SIFS+CTS frame+SIFS+data frame+SIFS+ACK frame) that is continuously transmitted thereafter using the duration information included in the RTS frame. Alternatively, if STA3 can eavesdrop on the CTS frame from STA2, STA3 can set the NAV timer for the frame transmission period (e.g., SIFS+data frame+SIFS+ACK frame) that is continuously transmitted thereafter using the duration information included in the CTS frame even though STA3 cannot eavesdrop on the RTS frame from STA1. That is, if STA3 can eavesdrop on one or more of the RTS frame or the CTS frame from one or more of STA1 or STA2, STA3 can set the NAV accordingly. When STA3 receives a new frame before the NAV timer expires, STA3 can update the NAV timer using the duration information included in the new frame. STA3 does not attempt channel access until the NAV timer expires.

[0095] When STA1 receives a CTS frame from STA2, STA1 may send a data frame to STA2 after SIFS, starting from the time point when reception of the CTS frame is completed. When STA2 successfully receives the data frame, STA2 may send an ACK frame to STA1 after SIFS as a response to the data frame. When the NAV timer expires, STA3 may determine whether the channel is being used by carrier sensing. When STA3 determines that the channel is not being used by other terminals during the DIFS period after the NAV timer expires, STA3 may attempt channel access after the contention window (CW) according to the random backoff has passed.

[0096] Figure 6 is a diagram for explaining an example of a frame structure used in a WLAN system to which the present disclosure can be applied.

[0097] With the help of instructions or primitives (meaning a set of instructions or parameters) from the MAC layer, the PHY layer can prepare a MAC PDU (MPDU) to be transmitted. For example, when a command requesting the PHY layer to start transmitting is received from the MAC layer, the PHY layer switches to a transmission mode, and configures information (e.g., data) provided from the MAC layer in the form of a frame and transmits it. In addition, when the PHY layer detects a valid preamble of a received frame, the PHY layer monitors the header of the preamble and transmits a command notifying the start of reception of the PHY layer to the MAC layer.

[0098] In this manner, information transmission / reception in the wireless LAN system is performed in the form of frames, and for this purpose, a PHY layer protocol data unit (PPDU) frame format is defined.

[0099] The basic PPDU frame may include a short training field (STF), a long training field (LTF), a signal (SIG) field, and a data field. The most basic (e.g., non-high throughput (HT)) PPDU frame format may consist of only L-STF (legacy STF), L-LTF (legacy-LTF), a SIG field, and a data field. In addition, depending on the type of PPDU frame format (e.g., HT mixed format PPDU, HT greenfield format PPDU, VHT (very high throughput) PPDU, etc.), additional (or different types of) STF, LTF, and SIG fields may be included between the SIG field and the data field (reference will be made later). Figure 7 Describe this).

[0100] STF is a signal used for signal detection, automatic gain control (AGC), diversity selection, precise time synchronization, etc., and LTF is a signal used for channel estimation and frequency error estimation. STF and LTF can be called signals for synchronization and channel estimation of the OFDM physical layer.

[0101] The SIG field may include a rate field and a length field, etc. The rate field may include information about the modulation and coding rate of the data. The length field may include information about the length of the data. In addition, the SIG field may include a parity bit, a SIG tail bit, etc.

[0102] The data field may include a service (SERVICE) field, a physical layer service data unit (PSDU) and a PPDU tail bit, and may also include padding bits if necessary. Some bits of the service field may be used for synchronization of the descrambler at the receiving end. The PSDU corresponds to the MAC PDU defined in the MAC layer and may include data generated / used in the upper layer. The PPDU tail bit may be used to return the encoder to the 0 state. The padding bit may be used to adjust the length of the data field in predetermined units.

[0103] MAC PDU is defined according to various MAC frame formats, and a basic MAC frame consists of a MAC header, a frame body, and a frame check sequence (FCS). A MAC frame may consist of a MAC PDU and be transmitted / received through a PSDU of a data portion of a PPDU frame format.

[0104] The MAC header includes a frame control field, a duration / ID field, an address field, etc. The frame control field may include control information required for frame transmission / reception. The duration / ID field may be set to the time for transmitting the corresponding frame, etc. For details of the sequence control, QoS control, and HT control subfields of the MAC header, refer to the IEEE 802.11 standard document.

[0105] The Null Data Packet (NDP) frame format means a frame format that does not include a data packet. That is, the NDP frame refers to a frame format that includes a physical layer convergence procedure (PLCP) header portion (i.e., STF, LTF, and SIG fields) in a common PPDU frame format and does not include the remaining portion (i.e., data field). The NDP frame may also be referred to as a short frame format.

[0106] Figure 7 is a diagram illustrating an example of a PPDU defined in the IEEE 802.11 standard to which the present disclosure can be applied.

[0107] In standards such as IEEE 802.11a / g / n / ac / ax, various types of PPDUs have been used. The basic PPDU format (IEEE 802.11a / g) includes L-LTF, L-STF, L-SIG, and data fields. The basic PPDU format may also be referred to as a non-HT PPDU format.

[0108] The HT PPDU format (IEEE 802.11n) additionally includes HT-SIG, HT-STF, and HT-LFT fields with respect to the basic PPDU format. Figure 7 The HT PPDU format shown in the figure may be referred to as an HT mixed format. In addition, an HT greenfield format PPDU may be defined, and this corresponds to a format consisting of HT-GF-STF, HT-LTF1, HT-SIG, one or more HT-LTFs, and a data field, excluding L-STF, L-LTF, and L-SIG (not shown).

[0109] An example of a VHT PPDU format (IEEE 802.11ac) additionally includes VHT SIG-A, VHT-STF, VHT-LTF, and VHT-SIG-B fields for the basic PPDU format.

[0110] Examples of HE PPDU formats (IEEE 802.11ax) additionally include repeated L-SIG (RL-SIG), HE-SIG-A, HE-SIG-B, HE-STF, HE-LTF, and packet extension (PE) fields with respect to the basic PPDU format. According to the detailed examples of the HE PPDU format, some fields may be excluded or their lengths may vary. For example, the HE-SIG-B field is included in the HE PPDU format for multi-user (MU), while the HE-SIG-B is not included in the HE PPDU format for single user (SU). In addition, the PPDU format based on HE trigger (TB) does not include the HE-SIG-B, and the length of the HE-STF field may vary to 8us. The extended range (HE ER) SU PPDU format does not include the HE-SIG-B field, and the length of the HE-SIG-A field may vary to 16us.

[0111] Figures 8 to 10 is a diagram for explaining an example of a resource unit of a WLAN system to which the present disclosure can be applied.

[0112] refer to Figures 8 to 10 , a resource unit (RU) defined in a wireless LAN system will be described. A RU may include multiple subcarriers (or tones). When a signal is transmitted to multiple STAs based on an OFDMA scheme, an RU may be used. In addition, an RU may be defined even when a signal is transmitted to one STA. An RU may be used for a data field, an STF, an LTF, etc. of a PPDU.

[0113] like Figures 8 to 10 As shown in , RUs corresponding to different numbers of tones (i.e., subcarriers) are used to construct some fields of a 20 MHz, 40 MHz, or 80 MHz X-PPDU (X is HE, EHT, etc.). For example, resources may be allocated in RU units as shown for the X-STF, X-LTF, and data fields.

[0114] Figure 8 is a diagram illustrating exemplary allocation of resource units (RUs) used on a 20 MHz frequency band.

[0115] like Figure 8As shown at the top of , 26-units (i.e., units corresponding to 26 tones) may be allocated. 6 tones may be used as a guard band in the leftmost band of the 20 MHz band, and 5 tones may be used as a guard band in the rightmost band of the 20 MHz band. In addition, 7 DC tones are inserted into the center band (that is, the DC band), and 26-units corresponding to each of the 13 tones may exist on the left and right sides of the DC band. In addition, 26-units, 52-units, and 106-units may be allocated to other bands. Each unit may be allocated for STA or user.

[0116] Figure 8 The RU allocation is used not only for the multi-user (MU) case but also for the single-user (SU) case, and in this case, a 242-unit can be used, such as Figure 8 In this case, three DC tones can be inserted.

[0117] exist Figure 8 In the examples, various sizes of RUs are illustrated, that is, 26-RU, 52-RU, 106-RU, 242-RU, etc., but the specific sizes of these RUs can be reduced or expanded. Therefore, in the present disclosure, the specific size of each RU (i.e., the number of corresponding tones) is exemplary and not restrictive. In addition, within a predetermined bandwidth (e.g., 20 MHz, 40 MHz, 80 MHz, 160 MHz, 320 MHz, ...) in the present disclosure, the number of RUs can vary according to the size of the RU. In the following description, Fig. 9 and / or Fig.10 The fact that the size and / or number of RUs can vary is related to Figure 8 The same example.

[0118] Fig. 9 is a diagram illustrating exemplary allocation of resource units (RUs) used on a 40 MHz frequency band.

[0119] As in Figure 8 As in the example using various RU sizes, you can also Fig. 9 In the example of , 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, etc. are used. In addition, 5 DC tones can be inserted at the center frequency, 12 tones can be used as a guard band in the leftmost band of the 40 MHz band, and 11 tones can be used as a guard band in the rightmost band of the 40 MHz band.

[0120] Additionally, as shown, when used for a single user, a 484-RU may be used.

[0121] Fig.10 is a diagram illustrating exemplary allocation of resource units (RUs) used on an 80 MHz frequency band.

[0122] As in Figure 8 and Fig. 9 As in the example using various RU sizes, you can also Fig.10 In the example of 26-RU, 52-RU, 106-RU, 242-RU, 484-RU, 996-RU, etc. are used. In addition, in the case of 80MHz PPDU, the RU allocation of HE PPDU and EHT PPDU can be different, and Fig.10 The example of FIG. 4 shows an example of RU allocation for an 80 MHz EHT PPDU. Fig.10 The scheme in which 12 tones in the example are used as a guard band in the leftmost band of the 80 MHz band and 11 tones are used as a guard band in the rightmost band of the 80 MHz band is the same as in the HE PPDU and the EHT PPDU. Unlike the HE PPDU in which 7 DC tones are inserted in the DC band and there is a 26-RU corresponding to each of the 13 tones on the left and right sides of the DC band, in the EHT PPDU, 23 DC tones are inserted in the DC band and there is a 26-RU on the left and right sides of the DC band. Unlike the HE PPDU in which one empty subcarrier exists between the 242-RUs instead of the center band, there are five empty subcarriers in the EHT PPDU. In the HE PPDU, one 484-RU does not include an empty subcarrier, but in the EHT PPDU, one 484-RU includes 5 empty subcarriers.

[0123] Additionally, as shown, when used for a single user, 996-RU may be used, and in this case, 5 DC tones are inserted as with HEPPDU and EHT PPDU.

[0124] exist Fig.10 In the example, the EHT PPDU on 160MHz can be configured with multiple 80MHz sub-blocks. The RU allocation for each 80MHz sub-block can be the same as Fig.10 If the 80 MHz sub-block of a 160 MHz or 320 MHz EHT PPDU is not punctured and the entire 80 MHz sub-block is used as a RU or part of a multiple RU (MRU), the 80 MHz sub-block can be used Fig.10 The 996-RU.

[0125] Here, the MRU corresponds to a group of subcarriers (or tones) consisting of multiple RUs, and the multiple RUs constituting the MRU may be RUs of the same size or RUs of different sizes. For example, a single MRU may be defined as 52+26-tones, 106+26-tones, 484+242-tones, 996+484-tones, 996+484+242-tones, 2×996+484-tones, 3×996-tones, or 3×996+484-tones. Here, the multiple RUs constituting one MRU may correspond to a small size (e.g., 26, 52, or 106) RU or a large size (e.g., 242, 484, or 996) RU. That is, one MRU including a small size RU and a large size RU may not be configured / defined. In addition, the multiple RUs constituting one MRU may be continuous in the frequency domain, or may not be continuous.

[0126] When an 80 MHz sub-block includes RUs less than 996-tones or a portion of the 80 MHz sub-block is punctured, the 80 MHz sub-block may use RU allocations other than the 996-tone RUs.

[0127] The RU of the present disclosure may be used for uplink (UL) and / or downlink (DL) communication. For example, when trigger-based UL-MU communication is performed, the STA (e.g., AP) that sends the trigger may allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA through trigger information (e.g., a trigger frame or a trigger response schedule (TRS)), and allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. Thereafter, the first STA may send a first trigger-based (TB) PPDU based on the first RU, and the second STA may send a second TB PPDU based on the second RU. The first / second TB PPDU may be sent to the AP in the same time period.

[0128] For example, when a DL MU PPDU is configured, the STA (e.g., AP) that transmits the DL MU PPDU may allocate a first RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the first STA, and allocate a second RU (e.g., 26 / 52 / 106 / 242-RU, etc.) to the second STA. That is, the transmitting STA (e.g., AP) may transmit the HE-STF, HE-LTF, and data fields for the first STA through the first RU within one MU PPDU, and transmit the HE-STF, HE-LTF, and data fields for the second STA through the second RU.

[0129] Information about the allocation of RUs may be signaled in HE PPDU format through HE-SIG-B.

[0130] Fig.11 An example structure of the HE-SIG-B field is illustrated.

[0131] As shown, the HE-SIG-B field may include common fields and user-specific fields. If HE-SIG-B compression is applied (e.g., full bandwidth MU-MIMO transmission), the common fields may not be included in the HE-SIG-B, and the HE-SIG-B content channel may include only user-specific fields. If HE-SIG-B compression is not applied, the common fields may be included in the HE-SIG-B.

[0132] The common field may include information about RU allocation (eg, RU assignment, RUs allocated for MU-MIMO, the number of MU-MIMO users (STAs), etc.).

[0133] The common field may include N*8 RU allocation subfields. Here, N is the number of subfields, N=1 in the case of 20 or 40MHz MU PPDU, N=2 in the case of 80MHz MU PPDU, N=4 in the case of 160MHz or 80+80MHz MU PPDU, and so on. An 8-bit RU allocation subfield may indicate the size (26, 52, 106, etc.) and frequency position (or RU index) of the RU included in the 20MHz band.

[0134] For example, if the value of the 8-bit RU Allocation subfield is 00000000, this may indicate that Figure 8 In the example, nine 26-RUs are allocated in sequence from the leftmost side to the rightmost side, if the value is 00000001, this may indicate that seven 26-RUs and one 52-RU are allocated in sequence from the leftmost side to the rightmost side, and if the value is 00000010, this may indicate that five 26-RUs, one 52-RU, and two 26-RUs are allocated in sequence from the leftmost side to the rightmost side.

[0135] As an additional example, if the value of the 8-bit RU Allocation subfield is 01000y2y1y0, this may indicate that Figure 8 In the example, one 106-RU and five 26-RUs are allocated from the leftmost to the rightmost. In this case, in the MU-MIMO scheme, multiple users / STAs can be allocated to the 106-RU. Specifically, up to 8 users / STAs can be allocated to the 106-RU, and the number of users / STAs allocated to the 106-RU is determined based on the 3-bit information (i.e., y2y1y0). For example, when the 3-bit information (y2y1y0) corresponds to a decimal value N, the number of users / STAs allocated to the 106-RU can be N+1.

[0136] Basically, one user / STA can be assigned to each of multiple RUs, and different users / STAs can be assigned to different RUs. For RUs larger than a predetermined size (e.g., 106, 242, 484, 996-tones, ...), multiple users / STAs can be assigned to one RU, and the MU-MIMO scheme can be applied to multiple users / STAs.

[0137] The set of user-specific fields includes information about how all users (STAs) of the corresponding PPDU decode their payloads. The user-specific field may contain zero or more user block fields. The non-end-user block field includes two user fields (ie, information to be used for decoding in two STAs). The end-user block field contains one or two user fields. The number of user fields may be indicated by the RU allocation subfield of the HE-SIG-B, the number of symbols of the HE-SIG-B, or the MU-MIMO user field of the HE-SIG-A. The user-specific field may be encoded separately from the common field or independently of the common field.

[0138] Fig.12 is a diagram for explaining a MU-MIMO method in which multiple users / STAs are assigned to one RU.

[0139] exist Fig.12 In the example, assume that the value of the RU allocation subfield is 01000010. This corresponds to the case where y2y1y0=010 in 01000y2y1y0. 010 corresponds to 2 in decimal (i.e., N=2) and may indicate that 3 (=N+1) users are allocated to one RU. In this case, one 106-RU and five 26-RUs may be allocated sequentially from the leftmost to the rightmost of a specific 20 MHz band / channel. Three users / STAs may be allocated to the 106-RU in MU-MIMO manner. As a result, a total of 8 users / STAs are allocated to the 20 MHz band / channel, and the user-specific field of the HE-SIG-B may include 8 user fields (i.e., 4 user block fields). Eight user fields may be assigned to an RU, such as Fig.12 shown.

[0140] The user field may be constructed based on two formats. The user field for MU-MIMO allocation may be constructed in a first format, and the user field for non-MU-MIMO allocation may be constructed in a second format. Fig.12 For example, user fields 1 to 3 may be based on a first format, and user fields 4 to 8 may be based on a second format. The first format and the second format may contain bit information of the same length (eg, 21 bits).

[0141] The user field of the first format (i.e., the format allocated for MU-MIMO) may be constructed as follows. For example, among all 21 bits of a user field, B0-B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11-B14 include spatial configuration information such as the number of spatial streams of the corresponding user, B15-B18 include modulation and coding scheme (MCS) information applied to the data field of the corresponding PPDU, B19 is defined as a reserved field, and B20 may include information about the coding type (e.g., binary convolutional coding (BCC) or low-density parity check (LDPC)) applied to the data field of the corresponding PPDU.

[0142] The user field of the second format (i.e., the format for non-MU-MIMO allocation) can be constructed as follows. For example, among all 21 bits of a user field, B0-B10 include identification information of the user (e.g., STA-ID, AID, partial AID, etc.), B11-B13 include information about the number of spatial streams (NSTS) applied to the corresponding RU, B14 includes information indicating whether beamforming is performed (or whether a beamforming control matrix is ​​applied), B15-B18 include modulation and coding scheme (MCS) information applied to the data field of the corresponding PPDU, B19 includes information indicating whether DCM (dual carrier modulation) is applied, and B20 may include information about the coding type (e.g., BCC or LDPC) applied to the data field of the corresponding PPDU.

[0143] The MCS, MCS information, MCS index, MCS field, etc. used in the present disclosure may be indicated by a specific index value. For example, the MCS information may be indicated as index 0 to index 11. The MCS information includes information about the constellation modulation type (e.g., BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM, etc.) and the coding rate (e.g., 1 / 2, 2 / 3, 3 / 4, 5 / 6, etc.). Information about the channel coding type (e.g., BCC or LDPC) may be excluded from the MCS information.

[0144] Fig.13 An example of a PPDU format to which the present disclosure can be applied is illustrated.

[0145] Fig.13The PPDU of the present disclosure may be referred to as various names such as EHT PPDU, transmitted PPDU, received PPDU, first type or Nth type PPDU. For example, the PPDU or EHT PPDU of the present disclosure may be referred to as various names such as transmitted PPDU, received PPDU, first type or Nth type PPDU. In addition, the EHT PPU may be used in an EHT system and / or a new wireless LAN system in which the EHT system is improved.

[0146] Fig.13 The EHT MU PPDU corresponds to a PPDU carrying one or more data (or PSDU) for one or more users. That is, the EHT MU PPDU can be used for SU transmission and MU transmission. For example, the EHT MU PPDU can correspond to a PPDU for one receiving STA or multiple receiving STAs.

[0147] exist Fig.13 In the EHT TB PPDU, the EHT-SIG is omitted compared to the EHT MU PPDU. Upon receiving a trigger for ULMU transmission (eg, a trigger frame or TRS), the STA may perform UL transmission based on the EHT TB PPDU format.

[0148] exist Fig.13 In the example of the EHT PPDU format, L-STF to EHT-LTF correspond to a preamble or a physical preamble and can be generated / transmitted / received / acquired / decoded in a physical layer.

[0149] The subcarrier frequency spacing of the L-STF, L-LTF, L-SIG, RL-SIG, Universal Signal (U-SIG), EHT-SIG fields (these are called pre-EHT modulation fields) can be set to 312.5kHz. The subcarrier frequency spacing of the EHT-STF, EHT-LTF, data and PE fields (these are called EHT modulation fields) can be set to 78.125kHz. That is, the tone / subcarrier index of the L-STF, L-LTF, L-SIG, RL-SIG, U-SIG and EHT-SIG fields can be indicated in units of 312.5kHz, and the tone / subcarrier index of the EHT-STF, EHT-LTF, data and PE fields can be indicated in units of 78.125kHz.

[0150] Fig.13 The L-LTF and L-STF can be used with Figure 6 to Figure 7 The corresponding fields of the PPDU described in are constructed identically.

[0151] Fig.13The L-SIG field may consist of 24 bits and may be used to transmit rate and length information. For example, the L-SIG field includes a 4-bit rate field, a 1-bit reserved bit, a 12-bit length field, a 1-bit parity field, and a 6-bit tail field. For example, the 12-bit length field may include information about the duration or length of the PPDU. For example, the value of the 12-bit length field may be determined based on the type of the PPDU. For example, for non-HT, HT, VHT, or EHT PPDUs, the value of the length field may be determined as a multiple of 3. For example, for HE PPDUs, the value of the length field may be determined as a multiple of 3 + 1 or a multiple of 3 + 2.

[0152] For example, the transmitting STA may apply BCC encoding based on the coding rate of 1 / 2 to 24 bits of information of the L-SIG field. Thereafter, the transmitting STA may obtain 48 BCC coded bits. BPSK modulation may be applied to the 48 coded bits to generate 48 BPSK symbols. The transmitting STA may map the 48 BPSK symbols to any position except the pilot subcarrier (e.g., {subcarrier index -21, -7, +7, +21}) and the DC subcarrier (e.g., {subcarrier index 0}). As a result, the 48 BPSK symbols may be mapped to subcarrier indexes -26 to -22, -20 to -8, -6 to -1, +1 to +6, +8 to +20, and +22 to +26. The transmitting STA may additionally map the signal of {-1, -1, -1, 1} to the subcarrier index {-28, -27, +27, +28}. The above signal can be used for channel estimation in the frequency domain corresponding to {-28, -27, +27, +28}.

[0153] The transmitting STA can construct the RL-SIG with the same structure as the L-SIG. BPSK modulation is applied to the RL-SIG. Based on the existence of the RL-SIG, the receiving STA can identify whether the received PPDU is a HE PPDU or an EHT PPDU.

[0154] exist Fig.13 After the RL-SIG, a universal SIG (U-SIG) may be inserted. The U-SIG may be referred to by various names such as a first SIG field, a first SIG, a first type SIG, a control signal, a control signal field, and a first (type) control signal.

[0155] The U-SIG may include N bits of information and may include information for identifying the EHT PPDU type. For example, the U-SIG may be configured based on two symbols (e.g., two consecutive OFDM symbols). Each symbol of the U-SIG (e.g., OFDM symbol) may have a duration of 4us, and the U-SIG may have a total duration of 8us. Each symbol of the U-SIG may be used to send 26 bits of information. For example, each symbol of the U-SIG may be sent and received based on 52 data tones and 4 pilot tones.

[0156] For example, through U-SIG (or U-SIG field), A-bit information (e.g., 52 uncoded bits) may be transmitted, the first symbol of U-SIG (e.g., U-SIG-1) may transmit the first X-bit information (e.g., 26 uncoded bits) of the total A-bit information, and the second symbol of U-SIG (e.g., U-SIG-2) may transmit the remaining Y-bit information (e.g., 26 uncoded bits) of the total A-bit information. For example, the transmitting STA may obtain the 26 uncoded bits included in each U-SIG symbol. The transmitting STA may generate 52 coded bits by performing convolution encoding (e.g., BCC encoding) based on a rate of R=1 / 2, and perform interleaving on the 52 coded bits. The transmitting STA may generate 52 BPSK symbols assigned to each U-SIG symbol by performing BPSK modulation on the interleaved 52 coded bits. Except for DC index 0, one U-SIG symbol may be transmitted based on 56 tones (subcarriers) from subcarrier index -28 to subcarrier index +28. The 52 BPSK symbols generated by the transmitting STA may be transmitted based on the remaining tones (subcarriers) except for the pilot tones -21, -7, +7, and +21.

[0157] For example, the A-bit information (e.g., 52 uncoded bits) sent by the U-SIG includes a CRC field (e.g., a 4-bit field) and a tail field (e.g., a 6-bit length field). The CRC field and the tail field may be sent through the second symbol of the U-SIG. The CRC field may be constructed based on the 26 bits of the first symbol allocated to the U-SIG and the remaining 16 bits in the second symbol excluding the CRC / tail field, and may be constructed based on a conventional CRC calculation algorithm. In addition, the tail field may be used to terminate the trellis of the convolutional decoder, and, for example, the tail field may be set to 0.

[0158] The bit information (e.g., 52 uncoded bits) transmitted by the U-SIG (or U-SIG field) may be divided into version-dependent bits and version-independent bits. For example, the size of the version-independent bits may be fixed or variable. For example, the version-independent bits may be assigned only to the first symbol of the U-SIG, or the version-independent bits may be assigned to the first symbol and the second symbol of the U-SIG. For example, the version-independent bits and the version-dependent bits may be referred to as various names such as the first control bit and the second control bit.

[0159] For example, the version-independent bit of the U-SIG may include a 3-bit physical layer version identifier (PHY version identifier). For example, the 3-bit PHY version identifier may include information related to the PHY version of the transmitted / received PPDU. For example, the first value of the 3-bit PHY version identifier may indicate that the transmitted / received PPDU is an EHT PPDU. In other words, when transmitting an EHT PPDU, the transmitting STA may set the 3-bit PHY version identifier to a first value. In other words, the receiving STA may determine that the received PPDU is an EHT PPDU based on the PHY version identifier having the first value.

[0160] For example, the version-independent bits of the U-SIG may include a 1-bit UL / DL flag field. A first value of the 1-bit UL / DL flag field is associated with UL communication, and a second value of the UL / DL flag field is associated with DL communication.

[0161] For example, the version-independent bits of the U-SIG may include information about a transmit opportunity length (TXOP) and information about a BSS color ID.

[0162] For example, if the EHT PPDU is classified into various types (e.g., EHT PPDU associated with SU mode, EHT PPDU associated with MU mode, EHT PPDU associated with TB mode, EHT PPDU associated with extended range transmission, etc.), information about the EHT PPDU type may be included in the version-related bit of the U-SIG.

[0163] For example, U-SIG may include information about the following items: 1) a bandwidth field containing information about the bandwidth, 2) a field containing information about the MCS scheme applied to the EHT-SIG, 3) an indication field containing information related to whether the DCM technology is applied to the EHT-SIG, 4) a field containing information about the number of symbols used for the EHT-SIG, 5) a field containing information about whether the EHT-SIG is constructed on all frequency bands, 6) a field containing information about the type of EHT-LTF / STF, and 7) a field indicating the EHT-LTF length and the CP length.

[0164] Can Fig.13 Preamble puncturing is applied to the PPDU of the primary 20 MHz band. Preamble puncturing means applying puncturing to some bands (e.g., the secondary 20 MHz band) among the entire band of the PPDU. For example, when sending an 80 MHz PPDU, the STA can apply puncturing to the secondary 20 MHz band of the 80 MHz band and send the PPDU only through the primary 20 MHz band and the secondary 40 MHz band.

[0165] For example, the pattern of preamble puncturing may be preset, for example, when the first puncturing pattern is applied, puncturing may be applied only to the auxiliary 20 MHz band within the 80 MHz band; for example, when the second puncturing pattern is applied, puncturing may be applied only to one of the two auxiliary 20 MHz bands included in the auxiliary 40 MHz band within the 80 MHz band; for example, when the third puncturing pattern is applied, puncturing may be applied only to the auxiliary 20 MHz band included in the main 80 MHz band within the 160 MHz band (or the 80 MHz + 80 MHz band). For example, when the fourth puncturing pattern is applied, within the 160 MHz band (or the 80 MHz + 80 MHz band), there is a main 40 MHz band included in the main 80 MHz band, and puncturing may be applied to at least one 20 MHz channel that does not belong to the main 40 MHz band.

[0166] Information about the preamble puncturing applied to the PPDU may be included in the U-SIG and / or the EHT-SIG. For example, the first field of the U-SIG may include information about the continuous bandwidth of the PPDU, and the second field of the U-SIG may include information about the preamble puncturing applied to the PPDU.

[0167] For example, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. If the bandwidth of the PPDU exceeds 80 MHz, the U-SIG may be independently constructed in units of 80 MHz. For example, if the bandwidth of the PPDU is 160 MHz, the PPDU may include a first U-SIG for a first 80 MHz band and a second U-SIG for a second 80 MHz band. In this case, the first field of the first U-SIG includes information about the 160 MHz bandwidth, and the second field of the first U-SIG includes information about the preamble puncturing applied to the first 80 MHz band (i.e., information about the preamble puncturing pattern). In addition, the first field of the second U-SIG includes information about the 160 MHz bandwidth, and the second field of the second U-SIG includes information about the preamble puncturing applied to the second 80 MHz band (i.e., information about the preamble puncturing pattern). The EHT-SIG after the first U-SIG may include information about preamble puncturing applied to the second 80 MHz frequency band (i.e., information about the preamble puncturing pattern), and the EHT-SIG after the second U-SIG may include information about preamble puncturing applied to the first 80 MHz frequency band (i.e., information about the preamble puncturing pattern).

[0168] Additionally or alternatively, the U-SIG and the EHT-SIG may include information about preamble puncturing based on the following method. The U-SIG may include information about preamble puncturing of all bands (ie, information about a preamble puncturing pattern). That is, the EHT-SIG does not include information about preamble puncturing, and only the U-SIG may include information about preamble puncturing (ie, information about a preamble puncturing pattern).

[0169] The U-SIG can be constructed in units of 20MHz. For example, if an 80MHz PPDU is constructed, the U-SIG can be duplicated. That is, the same 4 U-SIGs can be included in the 80MHz PPDU. PPDUs with bandwidths exceeding 80MHz can include different U-SIGs.

[0170] Fig.13 The EHT-SIG may include control information for the receiving STA. The EHT-SIG may be transmitted through at least one symbol, and one symbol may have a length of 4us. Information on the number of symbols used for the EHT-SIG may be included in the U-SIG.

[0171] The EHT-SIG may include Fig.11 and Fig.12 The technical features of HE-SIG-B are described. For example, Figure 8As in the example of , the EHT-SIG may include a common field and a user-specific field. The common field of the EHT-SIG may be omitted, and the number of user-specific fields may be determined based on the number of users.

[0172] As in Fig.11 As in the example of , the common field of EHT-SIG and the user-specific field of EHT-SIG can be encoded separately. One user block field included in the user-specific field can contain information for two user fields, but the last user block field included in the user-specific field can contain one or two user fields. That is, one user block field of EHT-SIG can contain up to two user fields. As in Fig.12 As in the example of , each user field may be associated with a MU-MIMO allocation or a non-MU-MIMO allocation.

[0173] With Fig.11 In the same manner as in the example of , the common field of the EHT-SIG may include a CRC bit and a tail bit. The length of the CRC bit may be determined as 4 bits, and the length of the tail bit may be determined as 6 bits and may be set to 000000.

[0174] As in Fig.11 As in the example of , the common field of the EHT-SIG may include RU allocation information. The RU allocation information may be information about the locations of the RUs to which multiple users (ie, multiple receiving STAs) are allocated. The RU allocation information may be configured in units of 9 bits (or N bits).

[0175] A mode in which the common field of the EHT-SIG is omitted may be supported. A mode in which the common field of the EHT-SIG is omitted may be referred to as a compressed mode. When the compressed mode is used, multiple users of the EHT PPDU (ie, multiple receiving STAs) may decode the PPDU (eg, the data field of the PPDU) based on non-OFDMA. That is, multiple users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) received via the same frequency band. When the non-compressed mode is used, multiple users of the EHT PPDU may decode the PPDU (eg, the data field of the PPDU) based on OFDMA. That is, multiple users of the EHT PPDU may receive the PPDU (eg, the data field of the PPDU) via different frequency bands.

[0176] The EHT-SIG may be constructed based on various MCS schemes. As described above, information related to the MCS scheme applied to the EHT-SIG may be included in the U-SIG. The EHT-SIG may be constructed based on the DCM scheme. The DCM scheme may reuse the same signal on two subcarriers to provide an effect similar to frequency diversity, reduce interference, and improve coverage. For example, modulation symbols applying the same modulation scheme may be repeatedly mapped on available tones / subcarriers. For example, a modulation symbol (e.g., a BPSK modulation symbol) applying a specific modulation scheme may be mapped to the first continuous half tone (e.g., the 1st to the 26th tone) among the N data tones (e.g., 52 data tones) allocated for the EHT-SIG, and a modulation symbol (e.g., a BPSK modulation symbol) applying the same specific modulation scheme may be mapped to the remaining continuous half tones (e.g., the 27th to the 52nd tone). That is, the modulation symbol mapped to the 1st tone and the modulation symbol mapped to the 27th tone are the same. As described above, information related to whether the DCM scheme is applied to the EHT-SIG (eg, a 1-bit field) may be included in the U-SIG. Fig.13 The EHT-STF can be used to enhance automatic gain control (AGC) estimation in a MIMO environment or an OFDMA environment. Fig.13 The EHT-LTF can be used to estimate channels in a MIMO environment or an OFDMA environment.

[0177] Information about the type of STF and / or LTF (including information about a guard interval (GI) applied to LTF) may be included in Fig.13 The U-SIG field and / or EHT-SIG field of the RFID tag may be used.

[0178] Can be based on Figures 8 to 10 Example construction of RU allocation Fig.13 PPDU (ie, EHT PPDU).

[0179] For example, based on Figure 8 The RU constructs an EHT PPDU to be sent on the 20 MHz band, that is, a 20 MHz EHT PPDU. Figure 8 As shown in , the RU positions of the EHT-STF, EHT-LTF, and data fields included in the EHT PPDU can be determined. Fig. 9 The RU constructs an EHT PPDU to be sent on the 40 MHz band, that is, a 40 MHz EHT PPDU. Fig. 9 As shown in , RU positions of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined.

[0180] Can be based on Fig.10 The RU constructs an EHT PPDU to be sent on the 80 MHz band, that is, an 80 MHz EHT PPDU. Fig.10 As shown in , RU positions of EHT-STF, EHT-LTF, and data fields included in the EHT PPDU may be determined. Fig.10 The tone plan for 80 MHz in may correspond to Fig. 9 Two repetitions of the tone plan for 40 MHz.

[0181] The tone plan for 160 / 240 / 320MHz can be repeated multiple times Fig. 9 or Fig.10 The mode is configured in the form of.

[0182] Fig.13 A PPDU can be identified as an EHT PPDU based on the following method.

[0183] The receiving STA may determine the type of the received PPDU as an EHT PPDU based on the following. For example, when 1) the first symbol after the L-LTF signal of the received PPDU is BPSK, 2) the RL-SIG that repeats the L-SIG of the received PPDU is detected, and 3) the result of applying the modulo 3 calculation to the value of the length field of the L-SIG of the received PPDU (i.e., the remainder after division by 3) is detected as 0, the received PPDU may be determined to be an EHT PPDU. When the received PPDU is determined to be an EHT PPDU, the receiving STA may determine the type of the received PPDU as an EHT PPDU based on Fig.13 In other words, the receiving STA can determine that the received PPDU is an EHT PPDU based on 1) the first symbol (BSPK) after the L-LTF signal, 2) the RL-SIG that is adjacent to the L-SIG field and is the same as the L-SIG, and 3) the L-SIG including the length field in which the result of applying modulo 3 is set to 0.

[0184] For example, the receiving STA may determine the type of the received PPDU as the HE PPDU based on the following: For example, when 1) the first symbol after the L-LTF signal is BPSK, 2) the RL-SIG repeating the L-SIG is detected, and 3) the result of applying modulo 3 to the length value of the L-SIG is detected as 1 or 2, the received PPDU may be determined as the HE PPDU.

[0185] For example, the receiving STA may determine the type of the received PPDU as non-HT, HT, and VHT PPDU based on the following: For example, when 1) the first symbol after the L-LTF signal is BPSK and 2) the RL-SIG repeating the L-SIG is not detected, the received PPDU may be determined as non-HT, HT, and VHT PPDU.

[0186] Fig.13 The PPDU can be used to send and receive various types of frames. For example, Fig.13 The PPDU can be used to (simultaneously) send and receive one or more of control frames, management frames, or data frames.

[0187] Trigger Frame

[0188] Fig.14 is a diagram illustrating an example format of a trigger frame to which the present disclosure may be applied.

[0189] The trigger frame may allocate resources for transmission of one or more TB PPDUs and request transmission of a TB PPDU.The trigger frame may also include other information required for the STA to send a TB PPDU in response.

[0190] Fig.14 (a) exemplarily shows an HE variant trigger frame. The trigger frame may include a common information field and a user information list field in the frame body.

[0191] Fig.14 The common information field shown as an example in (b) may include information that is generally applied to the transmission of one or more TB PPDUs requested by a trigger frame, such as the trigger type, UL length, the presence of subsequent trigger frames (e.g., more TFs), whether CS (channel sensing) is required, UL BW (bandwidth), etc.

[0192] For example, the encoding of the trigger type subfield indicating the trigger type may be implemented as shown in Table 1 below, but is not limited thereto.

[0193] [Table 1]

[0194] Trigger Type subfield value Trigger frame variant 0 Base 1 Beamforming Report Poll (BFRQ) 2 MU-BAR (Multi-User Block Ack Request) 3 MU-RTS (Multi-User Request to Send) 4 Buffer Status Report Polling 5 GCR (Multicast with Retry) MU-BAR 6 Bandwidth Query Report Poll (BQRP) 7 NDP Feedback Report Poll (NFRP) 8 Ranging 9-15 reserve

[0195] The user info list includes zero or more user info fields. Fig.14(c) exemplarily shows the HE variant user information field format. For example, the user information field may include an AID12 subfield, an RU allocation subfield, a UL FEC coding type subfield, a trigger dependent user field, etc. The RU allocation subfield may indicate the size and location of the RU / MRU. To this end, the RU allocation subfield may be interpreted together with the UL BW subfield of the common information field and the PS160 (primary / secondary 160MHz) subfield of the user information field.

[0196] Fig.14 (d) exemplarily shows the trigger dependent user information field on the base trigger frame. The MPDU MU interval factor subfield may be used to calculate a value multiplied by the minimum MPDU start interval. The TID aggregation limit subfield may indicate the maximum number of MPDUs allowed in an A-MPDU that a STA may carry in an HE TB PPDU and the maximum number of TIDs aggregated in the A-MPDU. The preferred AC subfield may indicate the minimum AC recommended for MPDU consolidation of the A-MPDU included in the HE TB PPDU sent in response to the trigger frame.

[0197] Probe Protocol Sequence

[0198] like Fig.15 As shown in (a), the HE non-trigger based (non-TB) sounding sequence is started by the HE beamformer transmitter with a single addressed HE NDP announcement frame including a STA information field, and after SIFS, the HE sounding NDP may be sent to the (single) HE beamformer receiver. The HE beamformer receiver may receive the HE sounding NDP from the HE beamformer transmitter and, after SIFS, respond by sending a HE Compressed Beamforming / CQI frame to the HE beamformer transmitter.

[0199] If the STA identified by the Receiver Address (RA) field is a mesh STA, AP, or IBSS STA, the AID11 subfield of the STA Information field may be configured to 0 or the AID of the STA identified by the RA field of the HE NDP announcement frame.

[0200] Specifically, the HE beamforming transmitter that starts the HE non-TB sounding sequence must send an HE NDP announcement frame with a single STA information (Info) field, and when the STA identified by the RA field is a mesh STA, AP, or IBSS member STA, the AID11 field value of the corresponding STA information field can be configured to 0 or the AID of the STA identified by the RA field instead of 2047. The HE beamforming transmitter can start the HE non-TB sounding sequence with the HE beamforming receiver to request SU feedback across the entire bandwidth. The HE beamforming transmitter may not start the HE non-TB using the HE NDP announcement frame with a partial BW information subfield showing less than the entire bandwidth.

[0201] like Fig.15 As shown in (b), the HE TB sounding sequence may be started by the HE beamformer transmitter using a broadcast HE NDP announcement frame with two or more STA information fields, a HE sounding NDP after SIFS, and a BFRP trigger frame after SIFS. One or more HE beamformer receivers may receive the BFPR trigger frame and respond with a HE compressed beamforming / CQI frame after SIFS. Here, the BFRQ trigger frame may include one or more user info fields identifying the HE beamformer receivers.

[0202] The HE beamformer transmitter that starts the HE TB sounding sequence may send a HE NDP announcement frame including two or more STA information fields and a RA field configured by a broadcast address. The HE beamformer transmitter may start the HE TB sounding sequence to request MU feedback across the entire bandwidth.

[0203] The HE beamformer transmitter may start the HE TB sounding sequence to request feedback variants only when the feedback variants are calculated based on parameters supported by the HE beamformer receiver, otherwise, the HE beamformer transmitter may not request feedback variants calculated based on parameters not supported by the HE beamformer receiver.

[0204] An HE beamformer transmitter that sends an HE NDP announcement frame to an HE beamformer receiver that is an AP, a TDLS peer STA, a mesh STA, or an IBSS STA may include one STA information (info) field on the HE NDP announcement frame and configure the AID11 field of the STA information field of the frame to 0.

[0205] The HE beamformer transmitter that is an AP and transmits an HE NDP announcement frame to one or more HE beamformer receivers may configure the AID11 field of the STA information field identifying the non-AP STA to the 11LSB of the AID of the non-AP STA. The HE NDP announcement frame may not include multiple STA information fields having the same value in the AID11 subfield.

[0206] The HE beamforming transmitter that sends the HE NDP announcement frame that starts the HE TB sounding sequence may include the STA information field with the AID11 subfield value of 2047 to indicate subchannels that are not allowed during the puncturing channel operation. When the STA information field is present, the STA information field with the AID11 value of 2047 may become the first STA information field of the frame. The HE beamforming transmitter that sends the HE NDP announcement frame may not include one or more STA information fields with the AID11 subfield value of 2047.

[0207] like Fig.15 As shown in (b) of FIG. 1 , the HE beamformer transmitter that starts the HE TB sounding sequence may send another BFRP trigger frame in the same TXOP. The HE beamformer transmitter may use the additional BFRP trigger frame to request an HE compressed beamforming / CQI report that was not processed in the previous BFRP trigger frame, or to request a retransmission of an HE compressed beamforming / CQI report. The HE beamformer transmitter may not send a BFRP trigger frame identifying the STA identified in the HE NDP announcement frame of the HE TB sounding sequence unless in the same TXOP as the HE TB sounding sequence.

[0208] In the HE TB sounding sequence, the STA Information field of the HE NDP announcement frame requesting SU or MU feedback may show the subcarrier grouping (Ng), the codebook size, and the number of columns (Nc) that the HE beamformer identified by the STA Information field will use to generate SU or MU feedback. Also, in the HE TB sounding sequence, the STA Information field of the HE NDP announcement frame requesting CQI feedback may show the Nc that the HE beamformer identified by the STA Information field will use to generate CQI feedback.

[0209] In addition, the trigger dependency common information subfield may not exist in the BFRQ trigger frame. The trigger dependency user information subfield of the BFRQ trigger frame may indicate feedback segment retransmission, and the bitmap subfield may indicate the request feedback segment of the HE compressed beamforming report.

[0210] If the bit at position n in the subfield (for LSB, n=0; for MSB, n=7) is 1, a feedback segment with n in the remaining feedback segment subfield of the HE MIMO control field can be requested; if the bit at position n in the subfield is 0, a feedback segment with n in the remaining feedback segment subfield of the HE MIMO control field can be requested.

[0211] Wireless LAN (WLAN) Sensing Process

[0212] The WLAN sensing process (hereinafter referred to as the sensing process) refers to a process of obtaining identification information about the surrounding environment based on the channel environment (or state) information included in the signal sent from the transmitting end to the receiving end. Each STA can provide additional services that can be applied in various forms in real life based on the information about the surrounding environment obtained through the sensing process.

[0213] Here, the information about the surrounding environment may include, for example, gesture recognition information, fall detection information, intrusion detection information, user motion detection, health monitoring information, or pet motion detection.

[0214] The sensing process may include at least one of a sensing session establishment phase, a sensing measurement establishment phase, a sensing measurement instance phase, a sensing measurement establishment termination phase, and a sensing session termination phase.

[0215] Here, a sensing session may be defined as a period of receiving / measuring a sensing signal after transmitting the sensing signal, and may include one or more sensing measurement instances.

[0216] A sensing session may include multiple subsessions, each of which may include a measurement phase and a reporting phase. Here, a subsession may be denoted as a sensing burst, a (sensing) measurement instance, or a measurement burst.

[0217] A STA that initiates a sensing process by transmitting a sensing measurement setup request frame or the like may be referred to as a sensing initiator, and a STA that participates in a sensing process (or a sensing session) in response to the sensing initiator may be referred to as a sensing responder.

[0218] The role of the STA that initiates the sensing process or participates in the sensing process can be a sensing transmitter and / or a sensing receiver. The sensing transmitter refers to the STA that sends the PPDU for measurement in the sensing process, and the sensing receiver refers to the STA that receives the PPDU received from the sensing transmitter in the sensing process and obtains the measurement result based on the PPDU.

[0219] SBP (Proxy Sensing) Process

[0220] SBP is a process that allows a non-AP STA to request WLAN sensing from an AP. An SBP initiator refers to a non-AP STA that sends an SBP request frame, and an SBP responder refers to an AP that receives an SBP request frame.

[0221] To establish the SBP process, the SBP initiator may send an SBP request frame to the AP (ie, the SBP responder). Upon receiving the SBP request frame, the SBP responder may accept or reject the SBP process.

[0222] For example, to accept the SBP process, the SBP responder may send an SBP response frame with a status code of 'SUCCESS' to the SBP initiator. As another example, to reject the SBP process, the SBP responder may send an SBP response frame with a status code of 'REQUEST_DECLINED' (or 'REQUEST_REJECTED' or 'REQUEST_WITH_SUGGESTED_CHANGES') to the SBP initiator.

[0223] In response to the SBP request frame, the SBP responder may send an SBP response frame to the SBP initiator within a predetermined period of time. If no SBP response frame is sent within the predetermined period of time or a status code 'REQUEST_DECLINED' (or 'REQUEST_REJECTED' or 'REQUEST_WITH_SUGGESTED_CHANGES') is sent, the SBP process establishment may be terminated.

[0224] The SBP responder that sends the SBP response frame with the status code 'SUCCESS' may initiate a wireless LAN sensing process with one or more non-AP STAs using one or more operation parameters indicated in the SBP request frame requesting the SBP process. The SBP initiator may participate in the wireless LAN process as a sensing responder.

[0225] The SBP initiator may request the SBP responder to initiate a wireless LAN sensing procedure that enables the sensing responder to perform sensing measurements using an NDP sent by another sensing responder.

[0226] After the last SBP report frame is sent by the SBP responder, the SBP process may be terminated. Additionally or alternatively, the SBP process may be terminated by sending an SBP terminate frame by the SBP initiator or the SBP responder.

[0227] R2R (Responder to Responder) Sensing Measurement Process

[0228] As described above, in order to perform sensing measurements, a non-AP STA (i.e., an SBP requesting STA or an SBP initiator) may send an SBP request frame to an AP (i.e., an SBP responder) to request the AP to perform sensing measurements on its behalf. The AP receiving the SBP request frame may send a signal to the non-AP STA via an SBP response frame as to whether to perform the SBP request.

[0229] According to the above process, the SBP initiator and the SBP responder can perform sensing measurement through the SBP process establishment. Here, the R2R (or SR2SR (sensing responder to sensing responder)) sensing process can be used to improve the performance of the sensing measurement and increase the efficiency of the sensing measurement.

[0230] In the basic wireless communication system, an operation for indicating the type of a sensing trigger frame through a sensing trigger subtype field of the sensing trigger frame and an operation for determining the role of a sensing STA are defined. However, in the case of the basic wireless communication system, an operation for performing an R2R detection step through an R2R trigger frame and an operation for indicating the role of each STA in the R2R detection step are not defined.

[0231] In the following, a procedure for performing R2R sensing measurements and how to define a new variant of a trigger frame used in the R2R sensing procedure is described.

[0232] Fig.16 1 is a diagram for describing a process in which a first STA performs a sensing process according to an embodiment of the present disclosure. Fig.16 and Fig.17 In the embodiment, the first STA may be a non-AP STA and the second STA may be an AP, but is not limited thereto.

[0233] The first STA may receive a sensing trigger frame including a sensing trigger subtype field from the second STA ( S1610 ).

[0234] For example, the sensing trigger frame may include a trigger dependency common information subfield, and the trigger dependency common information subfield may include a sensing trigger subtype field indicating a variant (or subtype) of the sensing trigger frame.

[0235] Here, the value of the sensing trigger subtype field may be set to 4. The value of the sensing trigger subtype field set to 4 may correspond to (ie, encode) information indicating that the sensing trigger subtype field is a SR2SR (sensing responder to sensing responder) sounding trigger frame.

[0236] That is, the first STA may receive the sensing trigger frame from the second STA. Then, the first STA may confirm that the sensing trigger frame is an SR2SR sounding trigger frame through the sensing trigger subtype field included in the sensing trigger frame.

[0237] The sensing trigger frame may include information indicating the role of the first STA in the SR2SR sounding phase. Specifically, the sensing trigger frame (ie, the SR2SR sounding trigger frame) may include a single transmitter user information field and one or more receiver user information fields.

[0238] The following description assumes (but is not limited to) that the SR2SR sounding trigger frame contains one transmitter user information field. The SR2SR sounding trigger frame may include one or more transmitter user information fields and one or more receiver user information fields.

[0239] For example, the transmitter user information field may include an AID12 / USD12 subfield, a Tx (transmit) / Rx (receive) subfield, an SR2SR Rep subfield, an SS allocation / RA (random access)-RU information subfield, a UL target received power subfield, and the like.

[0240] The one or more receiver user information fields may include an AID12 / USID12 subfield, a Tx / Rx subfield, and a TX AID12 / USID12 subfield.

[0241] The AID12 / USD12 subfield of the transmitter user information field may include the AID of the STA that performs the SR2SR sensing transmitter role (i.e., the non-AP STA that sends the NDP in the SR2SR probing phase). The TXAID12 / USD12 subfield of the receiver user information field may have the same value as the AID12 / USD12 subfield of the transmitter user information field.

[0242] The Tx / Rx subfield may indicate the role of the addressed SR2SR sensing responder in the SR2SR detection phase. That is, information indicating the role of the first STA may be indicated by a Tx / Rx subfield included in the transmitter user information field or the receiver user information field. The Tx / Rx subfield may consist of 1 bit, but is not limited thereto.

[0243] For example, a value of the Tx / Rx subfield of the transmitter user information field may be set to 0. A value of the Tx / Rx subfield of the receiver user information field may be set to 1.

[0244] The SR2SR Rep subfield may indicate the number of HE-LTF repetitions in the corresponding HE ranging NDP of the non-AP STA indicated in the AID12 / USID12 subfield. The SR2SR Rep subfield may be set to a value obtained by subtracting 1 from the number of HE-LTF repetitions.

[0245] The transmitter user information field may include at least one of information about a spatial stream allocated to the first STA (e.g., the number of spatial streams) or the size of the LTF. As an example, at least one of the information about the spatial stream allocated to the first STA or the information about the size of the LTF may be indicated by the SS allocation / RA-RU information.

[0246] Based on the role of the first STA being the SR2SR sensing transmitter, the transmitter user information field may include the AID of the first STA. Here, the first STA may decode the information included in the transmitter user information field (eg, Tx / Rx subfield, etc.).

[0247] As another example, based on the role of the first STA being an SR2SR sensing receiver (i.e., a non-AP STA receiving NDP in the SR2SR probing phase), the AID of the first STA may be included in a specific receiver user information field. In this case, the first STA may decode the information included in the corresponding receiver user information field (e.g., Tx / Rx subfield, etc.).

[0248] Before step S1610 and / or as in step S1610, the first STA may send an SR2SR field (e.g., SR2SR support (sub) field) indicating information that it supports SR2SR detection to the second STA. That is, the SR2SR support (sub) field may indicate whether the TB (trigger-based) sensing measurement instance includes an SR2SR detection phase.

[0249] Here, the SR2SR support (sub) field may be transmitted to the second STA through a frame related to sensing measurement setup (eg, a sensing measurement setup request / response frame, a sensing measurement setup query frame, etc.).

[0250] Additionally or alternatively, the SR2SR support (sub)field may be transmitted and received via an association request / response frame, a reassociation request / response frame, a probe response frame, or the like.

[0251] The first STA may transmit an SR2SR NDP to or receive an SR2SR NDP from at least one STA based on the sensing trigger frame in the SR2SR probing phase ( S1620 ).

[0252] When the role of the first STA is a SR2SR sensing transmitter, the first STA may transmit a SR2SR NDP to at least one STA (ie, other non-AP STAs acting as SR2SR sensing receivers). Here, the at least one non-AP STA may perform sensing measurements based on the SR2SR NDP.

[0253] Here, at least one STA acting as an SR2SR sensing receiver may also receive an SR2SR sensing trigger frame from a second STA. Here, each of at least one receiver information field included in the SR2SR sensing trigger frame may correspond to each of the at least one STA acting as an SR2SR sensing receiver.

[0254] As another example, if the role of the first STA is a SR2SR sensing receiver, the first STA may receive a SR2SR NDP from a STA performing the role of a SR2SR sensing transmitter. Here, the first STA may perform sensing measurement based on the received SR2SR NDP.

[0255] The SR2SR NDP may be transmitted in a bandwidth of 160 MHz or less, but is not limited thereto, and may also be transmitted in a bandwidth of 320 MHz or more. Figure 6 , Figure 7 and Fig.13 However, this is only one implementation, and the SR2SR NDP may also be configured based on a separate PPDU format.

[0256] For example, if the role of the first STA is an SR2SR sensing receiver, the first STA may receive a frame requesting a sensing measurement result performed through the SR2SR NDP from the second STA. Here, the first STA may transmit a frame including the sensing measurement result to the second STA.

[0257] exist Fig.16 The method performed by the first STA described in the example of Figure 1 The first device (100) performs. For example, Figure 1 One or more processors (102) of the first device (100) may be configured to receive a sensing trigger frame including a sensing trigger subtype field from a second STA through one or more transceivers (106). The one or more processors (102) may be configured to send an SR2SR NDP to at least one STA through one or more transceivers (106) based on the sensing trigger frame in an SR2SR probing phase, or to receive an SR2SR NDP from at least one STA through one or more transceivers (106).

[0258] In addition, one or more memories (104) of the first device (100) may store instructions for executing the operation when executed by one or more processors (102). Fig.16 Instructions for the methods described in the examples.

[0259] Fig.17is a diagram for describing a process in which a second STA performs a sensing process according to one embodiment of the present disclosure.

[0260] The second STA may transmit a sensing trigger frame including a sensing trigger subtype field to a plurality of STAs including the first STA ( S1710 ).

[0261] For example, the second STA may configure an SR2SR sounding trigger frame, which is a variant of a sensing trigger frame. The second STA may send an SR2SR sounding trigger frame including a single transmitter user field and one or more receiver user fields to multiple STAs including the first STA.

[0262] The second STA may receive a measurement result of the SR2SR NDP transmitted based on the sensing trigger frame from at least one STA among the plurality of STAs in the SR2SR probing phase ( S1720 ).

[0263] Here, at least one STA among the plurality of STAs may refer to one or more SR2SR sensing receivers that perform sensing measurement based on the NDP transmitted by the SR2SR sensing transmitter.

[0264] Specifically, the second STA may transmit a frame requesting a sensing measurement result performed through the SR2SR NDP to at least one STA as an SR2SR sensing receiver. The second STA may receive a frame including the sensing measurement result from the at least one STA.

[0265] As an example of the present disclosure, the second STA may be a proxy sensing (SBP) responder that receives an SBP request frame from an SBP initiator (eg, a specific non-AP STA).

[0266] The SBP request frame may include parameters related to the SBP process and the sensing measurement. The second STA may send an SBP response frame to the SBP initiator. At this time, the SBP response frame sent from the SBP responder to the SBP initiator may include a status code for at least one of the parameters related to the SBP process or the sensing measurement.

[0267] exist Fig.17 The method performed by the second STA described in the example of Figure 1 The second device (200) is executed. For example, Figure 1The one or more processors (202) of the second device (200) may be configured to send a sensing trigger frame including a sensing trigger subtype field to a plurality of STAs including the first STA through one or more transceivers (206). The one or more processors (202) may be configured to receive a measurement result of an SR2SR NDP sent based on the sensing trigger frame from at least one STA among the plurality of STAs through one or more transceivers (206) in the SR2SR probing phase.

[0268] In addition, the one or more memories (204) of the second device (200) may store instructions for executing the operation when executed by the one or more processors (202). Fig.17 Instructions for the methods described in the examples.

[0269] Hereinafter, an SBP procedure, a procedure for performing R2R sensing measurement, and a configuration of a trigger frame related thereto are described in detail.

[0270] Implementation Method 1

[0271] Embodiment 1 relates to the operation and sensing measurement establishment steps according to the SBP process.

[0272] The SBP initiator and the SBP responder that perform the SBP process can send and receive SBP request / response frames between each other to send and receive information about performing the SBP in the SBP process establishment phase. Fig.18 The illustrated configuration is used to perform the SBP process establishment phase of the SBP process.

[0273] like Fig.18 As shown, the SBP initiator (ie, non-AP STA) may send an SBP setup request frame to the sensing SBP responder (ie, AP) to request sensing measurements during the SBP process setup phase.

[0274] The SBP setup request frame may include information about sensing parameters for performing sensing measurement. The sensing parameters may include information about whether R2R measurement is supported, information about Tx or Rx operation during R2R measurement, and / or an indication of a role during R2R measurement.

[0275] The SBP responder (i.e., AP) that receives the SBP request frame may send an SBP response frame to the SBP initiator, including information about parameters related to performing the SBP process, information about whether R2R measurement is supported, information about TX or RX operation during the R2R measurement, and indication information about the role during the R2R measurement.

[0276] Information about whether R2R measurement is supported may be indicated by an R2R support field. For example, the R2R support field may consist of 1 bit. If the R2R support field value is set to 1 (or 0), it may indicate that R2R measurement is supported. If the R2R support field value is set to 0 (or 1), this may indicate that R2R measurement is not supported.

[0277] Additionally or alternatively, the R2R Support field may be composed of a Tx Support field and an Rx Support field, each including information on a Tx operation and an Rx operation of the non-AP STA during the R2R measurement.

[0278] Here, the information about the Tx operation indicated by the Tx Support field may include information about whether the non-AP STA operates as a (R2R) sensing transmitter during R2R measurement. The information about the Rx operation indicated by the Rx Support field may include information about whether the non-AP STA operates as a (R2R) sensing receiver during R2R measurement.

[0279] For example, the TX Support field may include 1 bit and indicate whether the transmitter operates as an R2R sensing transmitter in R2R measurement (ie, whether R2R NDP transmission is supported, etc.).

[0280] For example, if the TX Support field value is set to 1, this may indicate support for R2R NDP transmission (or operation as a transmitter in R2R measurement). If the TX Support field value is set to 0, this may indicate that R2R NDP transmission (or operation as a transmitter in R2R measurement) is not supported.

[0281] The Rx Support field may indicate whether the receiver acts as an R2R sensing receiver in R2R measurement (ie, whether it performs an operation of receiving and reporting an NDP transmitted by a non-AP, etc.), and may consist of 1 bit.

[0282] For example, if the Rx Support field value is set to 1, this may indicate that an operation of performing NDP measurement and sending feedback (ie, operating as an R2R sensing receiver in R2R measurement) is supported. If the Rx Support field value is set to 0, this may indicate that an operation of performing NDP measurement and sending feedback (ie, operating as an R2R sensing receiver in R2R measurement) is not supported.

[0283] As described above, the R2R support field (i.e., 2 bits) may be composed of a Tx support field and an Rx support field. Here, if the non-AP or / and AP do not support R2R, the 2-bit value constituting the R2R support field may be set to 0. That is, the 2-bit value constituting the R2R support field set to 0 may indicate that the corresponding non-AP or / and AP do not support R2R.

[0284] As another example, the R2R support field may be configured as a single field without distinguishing between Tx and Rx subfields. Also, the R2R support field may indicate whether the corresponding non-AP or / and AP operates as an R2R sensing transmitter or as an R2R sensing receiver.

[0285] For example, assuming that the behavior of the non-AP STA in the R2R measurement process is indicated by 1 bit (e.g., R2R support field or / and separate Tx / Rx indication field, etc.). If the corresponding 1-bit value is set to 0, it may indicate that the non-AP STA operates as an R2R sensing receiver. If the corresponding 1-bit value is set to 1, it may indicate that the non-AP STA operates as an R2R sensing transmitter.

[0286] For example, if the operation of the non-AP STA is indicated by this 1 bit (eg, Tx / Rx indication field), this 1 bit can be used together with the R2R support field to indicate whether R2R measurement is supported and what operation the non-AP performs when measuring R2R.

[0287] As another example, the Tx / Rx Indication field may indicate the role of the non-AP STA in the R2R measurement. Therefore, the Tx / Rx Indication field may be used for R2R role indication, and the name of the Tx / Rx Indication field may be defined as an R2R role indication (sub)field.

[0288] When establishing the R2R measurement process, the R2R support indication and the Tx / Rx indication (or R2R role indication) may be sent and received through the request frame and the response frame. If the R2R support indication field value is set to 0, and therefore R2R measurement is not supported, the decoding of the Tx / Rx indication (or R2R role indication) field may be ignored or retained.

[0289] Implementation Method 2

[0290] Embodiment 2 relates to a method for exchanging information related to R2R measurement in a sensing measurement setup procedure.

[0291] Specifically, whether to perform R2R measurement can be set in the sensing measurement establishment phase performed by the SBP responder (i.e., AP) together with the non-AP STA to perform sensing measurement after the SBP establishment phase. That is, in the sensing measurement establishment process, information related to R2R measurement can be exchanged between the AP and the non-AP STA.

[0292] Here, whether to perform / support R2R measurement and the Tx / Rx operation / role of the non-AP STA in the R2R measurement may be indicated by the R2R support field and the Tx / Rx indication (or R2R role indication) field.

[0293] And, at least one of the R2R support field and the Tx / Rx indication (or R2R role indication) field may be included in the sensing measurement parameter field. That is, at least one of the R2R support field and the Tx / Rx indication (or R2R role indication) field may be transmitted and received through the sensing measurement parameter field included in the sensing measurement setup request frame / response frame.

[0294] The R2R indication field and / or the Tx / Rx indication (or R2R role indication) field included in the sensing measurement setup request / response frame may be configured as described in Embodiment 1.

[0295] Through the measurement setup between the SBP responder (ie, AP) and the non-AP STA that participates in the SBP and performs sensing measurement, the AP can obtain information about the non-AP STA that supports the R2R measurement.

[0296] Implementation 3

[0297] Embodiment 3 relates to a process for an AP to perform sensing measurement between non-AP STAs supporting R2R measurement.

[0298] As described above, information on whether the R2R measurement is supported and the role of the non-AP STA in the R2R measurement may be exchanged in the SBP procedure establishment phase or / and the sensing measurement establishment phase.

[0299] As an example of the present disclosure, the AP (ie, SBP responder) may trigger NDP transmission by sending a trigger frame to a specific non-AP STA (eg, a non-AP STA that acts as a sensing responder / initiator in the SBP process). Operations related thereto are described in detail in Embodiment 3-1.

[0300] As another example of the present disclosure, the R2R measurement process may be performed by an AP that transmits an SBP trigger frame including a user field of one or more non-AP STAs for performing R2R measurement. Operations related thereto are described in detail in Embodiment 3-2.

[0301] As another example of the present disclosure, the AP may request a non-AP STA that performs R2R measurement to perform R2R measurement by sending an R2R request frame. Operations related thereto will be described in detail in Embodiment 3-3.

[0302] Implementation Method 3-1

[0303] like Fig.19As shown, the AP (ie, SBP responder) can trigger NDP transmission by sending a trigger frame to the non-AP STA1 acting as a responder / initiator in the SBP process. The non-AP STA1 can perform R2R measurement by sending NDP to the non-AP STA2.

[0304] Specifically, the AP that identifies the non-AP STA supporting the R2R measurement through the SBP process establishment may request NDP transmission of the non-AP STA1 by sending a trigger frame to the non-AP STA1 to perform the R2R measurement in the SBP.

[0305] like Fig.19 As shown, the trigger frame sent by the AP to request NDP transmission to the non-AP STA1 performing SBP can be defined as an SBP sensing trigger variant of the sensing trigger frame.

[0306] As another example, a variant of the sensing trigger frame sent by the AP to request NDP transmission to the non-AP STA1 may be a sensing trigger variant for R2R measurement / transmission.

[0307] Here, the sensing trigger variant for R2R measurement / transmission may be defined as an R2R sensing trigger variant or an R2R probing trigger variant.

[0308] The trigger frame defined as described above (ie, the trigger frame defined as a R2R sensing / detection trigger variant) is not limited to the SBP process and can also be used for a separate R2R sensing process.

[0309] For the convenience of explaining the present disclosure, the trigger frame sent by the AP is named as SBP sensing trigger variant, but is not limited thereto. The trigger frame sent by the AP may be defined as a sensing trigger frame for R2R measurement transmission as described above (i.e., a trigger frame defined as a R2R sensing / detection trigger variant).

[0310] Furthermore, the trigger frame transmitted by the AP is not limited to the SBP process and the subsequent R2R measurement process, and may also be applied to a separate R2R process.

[0311] The SBP process trigger variant may be indicated by the trigger dependency common information subfield of the sensing trigger frame. For example, as shown in Table 2 below, the SBP process trigger variant may be indicated by the sensing trigger subtype field included in the trigger dependency common information subfield.

[0312] [Table 2]

[0313] Sensor Trigger Subtype Subfield Value Sensor Trigger Frame Variants 0 polling 1 Detection 2 Report 3 SBP / R2R 4-15 Reserve

[0314] However, Table 2 is only one embodiment, and the SBP sensing trigger variant (or R2R sensing trigger variant) may be indicated by another sensing trigger subtype subfield value (e.g., one of 4 to 15). As an example of the present disclosure, when the AP sends a trigger frame set to the SBP / R2R sensing trigger (sub) variant, the TA (transmitter address) of the trigger frame may be set to the address of the AP, and the RA (receiver address) may be set to the broadcast ID.

[0315] The trigger frame set to SBP / R2R sensing trigger (sub) variant may include a user field. Fig.19 As shown, the non-AP STA1 and the non-AP STA2 that perform / support the R2R sensing measurement may determine to perform the R2R sensing measurement by receiving a trigger frame (for the R2R sensing measurement) transmitted by the AP.

[0316] The trigger frame set to SBP / R2R sensing trigger (sub) variant may include an R2R sensing indication bit to indicate R2R sensing measurement. In this case, the R2R sensing indication bit may be sent by including it in the trigger-dependent common information subfield of the corresponding trigger frame.

[0317] As another example of the present disclosure, when a trigger frame set to an SBP / R2R sensing trigger (sub) variant is sent by an AP, the TA of the trigger frame may be set to the address of the AP, and the RA may be set to a non-AP STA (e.g., non-APSTA1) that sends the NDP (i.e., the address of the non-AP STA).

[0318] refer to Fig.19 , since the RA of the trigger frame is set to the non-AP STA1 that transmits the NDP, a separate signal may be transmitted before the trigger frame is transmitted to notify the non-AP STA2 that performs the R2R sensing to perform the R2R sensing.

[0319] For example, the AP may send a signal notifying R2R sensing performance only to non-AP STA1 and non-AP STA2 configured for R2R sensing or non-AP STA2 before sending a trigger frame. Non-AP STA2 that performs / supports R2R sensing and receives the signal may confirm that R2R sensing is performed and may prepare to receive NDP for R2R sensing.

[0320] As described above, the trigger frame configured as a SBP / R2R sensing trigger (sub) variant is used to trigger NDP transmission and may include a user field.

[0321] For example, the user field of the trigger frame (for SBP / R2R) may include AID information, BW / allocation information, 'GI+LTF size (or / and type)' information, and NSS (number of spatial streams) information.

[0322] Here, the AID information may include ID information of a non-AP STA for transmitting an NDP for R2R measurement.

[0323] And, the BW / allocation information may include BW information for NDP transmission. The BW / allocation information may consist of the same 2 bits as the UL BW of the common information field of the trigger frame (i.e., bits indicating the BW for transmitting the NDP). The BW for transmitting the NDP may indicate one of 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 80+80 MHz.

[0324] As another example, the BW / allocation information may consist of 3 bits. In this case, the BW / allocation information may also indicate a BW of 320 MHz or higher as the BW at which the NDP is transmitted.

[0325] For example, the BW over which the NDP indicated by the BW / allocation information is transmitted may be configured to be less than or equal to the BW of the UL BW of the common information field of the trigger frame.

[0326] For example, the BW / allocation information included in the user information field in the corresponding trigger frame may include puncturing information. That is, the BW / allocation information may be configured with 5 bits to indicate the puncturing information. The non-AP STA may check the BW in which the NDP is transmitted through the UL BW subfield of the common information field of the corresponding trigger frame, and may check the information of puncturing within the BW through the BW / allocation information field.

[0327] The 'GI+LTF size (or / and type)' information may be used to indicate information about the GI and LTF sizes used when transmitting NDP. Specifically, the non-AP STA transmits NDP using the SU format and may confirm the GI and LTF sizes through the 'GI+LTF size (or / and type)' information.

[0328] Here, the 'GI+LTF size (or / and type)' information included in the user information field may be configured to be different from the 'GI+LTF type' information transmitted through the common information field of the corresponding trigger frame.

[0329] For example, the 'GI+LTF size (or / and type)' information may consist of 2 bits, as shown in Table 3 below.

[0330] [Table 3]

[0331] GI+LTF size subfield value Sensor Trigger Frame Variants 0 2x HE LTF+0.8us GI 1 2x HE LTF+1.6us GI 2 4x HE LTF+3.2us GI 3 Reserve

[0332] As another example of the present disclosure, when a trigger frame set to an SBP / R2R sensing trigger (sub) variant is sent, the 'GI+LTF size subfield' of the common information field of the trigger frame may be configured according to the above configuration (e.g., according to the configuration of Table 3, etc.). Then, the 'GI+LTF size subfield' of the common information field of the trigger frame may indicate information about the GI and LTF type (or / and size) of the NDP transmission using the SU format.

[0333] For example, if the common information field of the trigger frame includes the 'GI+LTF size subfield' configured as described above, the user information field of the trigger frame may not include the 'GI+LTF size subfield'.

[0334] The NSS information may indicate the number of spatial streams allocated when the NDP is transmitted. For example, the NSS information may consist of 3 bits and may represent one of 1 to 8 as the number of spatial streams.

[0335] refer to Fig.19 , the non-AP STA1 receiving the SBP / R2R (or SR2SR) sensing trigger frame from the AP may send an NDP for R2R measurement to another non-AP STA. Here, the NDP may be configured using the SU PPDU format.

[0336] For example, the NDP transmitted by the non-AP STA1 may be defined as an R2R NDP, and the R2R NDP transmitted after receiving the trigger frame may be configured using the HE NDP format or the EHT NDP format.

[0337] Non-AP STA2 receiving the R2R NDP transmitted by non-AP STA1 may perform channel measurement between non-AP STA1 and non-AP STA 2 using the NDP. In order to receive feedback on channel information measured by non-AP STA2, the AP may transmit a feedback request frame requesting feedback to non-AP STA2.

[0338] The non-AP STA2 that has received the feedback request frame may transmit CSI (Channel State Information) to the AP using a report parameter included in the feedback request frame.

[0339] like Fig.19 As shown, each frame (e.g., trigger frame, NDP, feedback (request) frame, etc.) may be sent at a SIFS interval, but is not limited thereto. That is, various types of IFS may be applied to the transmission interval of each frame. For example, an IFS having an interval greater than SIFS may be used for the intervals of feedback request frames and feedback report frames.

[0340] Implementation 3-2

[0341] When the AP transmits an SBP / R2R (or SR2SR) sensing trigger frame to perform R2R measurement, the trigger frame may include a user (information) field for two non-AP STAs performing the R2R measurement.

[0342] The SBP / R2R trigger frame may be a (sub) variant of the sensing trigger frame. The trigger frame may include information of a Tx non-AP STA (i.e., a non-AP STA operating as a transmitter) and an Rx non-AP STA (i.e., a non-AP STA operating as a receiver) performing the R2R process.

[0343] As described in Embodiment 3-1, the indication of the (sub) variant of the corresponding trigger frame (i.e., the SBP (sub) variant or / and (sub) variant for R2R measurement / transmission) may be performed via the trigger-dependent common information field of the sensing trigger frame (i.e., the sensing trigger subtype subfield of the trigger-dependent common information field).

[0344] The trigger frame defined as described above (ie, the trigger frame defined as a R2R sensing / detection trigger variant) is not limited to the SBP process and can also be used for a separate R2R sensing process.

[0345] For the convenience of explaining the present disclosure, the trigger frame sent by the AP is named as SBP sensing trigger (sub) variant, but is not limited thereto. The trigger frame sent by the AP can be defined as a sensing trigger frame for R2R measurement transmission as described above (i.e., a trigger frame defined as a R2R sensing / detection trigger variant).

[0346] Furthermore, the trigger frame transmitted by the AP is not limited to the SBP process and the subsequent R2R measurement process, and may also be applied to a separate R2R process.

[0347] As an example of the present disclosure, when a trigger frame set to an SBP / R2R sensing trigger (sub)variant is sent by an AP, the TA of the trigger frame may be set to the address of the AP, and the RA may be set to a broadcast ID or a multicast ID.

[0348] The trigger frame set to the SBP / R2R sensing trigger (sub) variant may include multiple user (information) fields (e.g., two user (information) fields). As an example, the user (information) field included in the trigger frame may consist of user (information) fields for TxSTA and Rx STA.

[0349] The user (information) field for Tx STA and / or Rx STA may include AID information, Tx / Rx operation or R2R role indication information, BW / allocation information, 'GI+LTF size (or / and type)' information, NSS information, and measurement ID information.

[0350] Here, the AID information may include ID information of a non-AP STA for performing R2R measurement. The AID information may include an ID for a Tx non-AP STA or an Rx non-AP STA.

[0351] The Tx / Rx operation or R2 role indication information may include information for indicating a role or Tx / Rx operation of a non-AP STA during R2R measurement.

[0352] For example, the Tx / Rx operation or R2R role indication information may consist of 1 bit. When the bit value corresponding to the Tx / Rx operation or R2R role indication information is set to 0 (or 1), this may indicate an Rx operation or a receiver role. And, when the bit value corresponding to the Tx / Rx operation or R2R role indication information is set to 1 (or 0), this may indicate a Tx operation or a transmitter role.

[0353] The bit value (or field including the bit) corresponding to the Tx / Rx operation or R2R role indication information included in the user (information) field for the Tx non-AP STA may always be set to 1 (or 0). Also, the bit value (or field including the release bit) corresponding to the Tx / Rx operation or R2R role indication information included in the user (information) field for the Rx non-AP STA may always be set to 0 (or 1).

[0354] The BW / allocation information may include BW information (e.g., feedback) for NDP transmission / reception. The BW / allocation information may consist of the same 2 bits as the UL BW of the common information field of the trigger frame described in Embodiment 1 (i.e., bits indicating the BW on which the NDP is transmitted). The BW on which the NDP is transmitted may indicate one of 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 80+80 MHz.

[0355] As another example, the BW / allocation information may consist of 3 bits. In this case, the BW / allocation information may also indicate a BW of 320 MHz or higher as the BW on which the NDP is transmitted.

[0356] For example, the BW on which the NDP is transmitted indicated by the BW / allocation information may be configured as a BW that is less than or equal to the UL BW of the common information field of the trigger frame.

[0357] For example, the BW / allocation information included in the user information field in the corresponding trigger frame may include puncturing information. That is, the BW / allocation information may be configured with 5 bits to indicate the puncturing information. The non-AP STA may identify the BW in which the NDP is transmitted through the UL BW subfield of the common information field of the corresponding trigger frame, and may identify information of puncturing within the BW through the BW / allocation information field.

[0358] The 'GI+LTF size (or / and type)' information may be used to indicate information about the GI and LTF sizes used when transmitting NDP. Specifically, the non-AP STA transmits NDP using the SU format and may confirm the GI and LTF sizes through the 'GI+LTF size (or / and type)' information.

[0359] Here, the 'GI+LTF size (or / and type)' information included in the user information field may be configured to be different from the 'GI+LTF type' information transmitted through the common information field of the corresponding trigger frame.

[0360] For example, as shown in Table 3, the 'GI+LTF size (or / and type)' information may consist of 2 bits.

[0361] As another example of the present disclosure, when a trigger frame set to an SBP / R2R sensing trigger (sub) variant is to be sent, the 'GI+LTF size subfield' of the common information field of the trigger frame may be configured according to the above configuration (eg, according to the configuration of Table 3, etc.).

[0362] In addition, the 'GI+LTF size subfield' of the common information field of the trigger frame may indicate information on the GI and LTF type (or / and size) transmitted using the NDP of the SU format.

[0363] For example, if the common information field of the trigger frame includes the 'GI+LTF size subfield' configured as described above, the user information field of the trigger frame may not include the 'GI+LTF size subfield'.

[0364] The NSS information may indicate the number of spatial streams allocated when the NDP is transmitted. For example, the NSS information may consist of 3 bits and may indicate one of 1 to 8 as the number of spatial streams.

[0365] The measurement ID may be composed of ID information which is information for indicating R2R measurement. The ID indicated by the measurement ID may be set to an establishment ID determined during the R2R process establishment, or may be set to a sensing measurement establishment ID.

[0366] refer to Fig. 20, the AP may send a trigger frame including two user (information) fields to the non-AP STAs performing / supporting R2R (e.g., non-AP STA 1 and non-AP STA 2). The non-AP STAs performing / supporting R2R measurement (e.g., non-AP STA 1 and non-AP STA 2) may check the AID and Tx / Rx operation or R2R role indication information included in the corresponding user information field to confirm what operation they perform (or what role they play) during the R2R measurement.

[0367] As described in Embodiment 1, a non-AP STA that detects performance of R2R measurement through a trigger frame transmitted by an AP may transmit and receive an NDP based on information received through the trigger frame.

[0368] The subsequent process (for example, a process for measuring a channel and reporting it via NDP) may be configured in the same manner as the process described in Embodiment 1. If the measurement ID information is included in the trigger frame, an ID according to the measurement ID information may be transmitted and received by being included in a feedback request frame and a feedback report frame.

[0369] Implementation 3-3

[0370] For R2R measurement, the AP may send an R2R request frame to a non-AP STA that performs / supports R2R measurement identified by establishing the SBP process. That is, the R2R request frame may be sent to request the non-AP STA to perform an R2R request.

[0371] In the R2R measurement phase, TF (Trigger Frame) detection may be performed, but is not limited thereto, and NDPA (NDP Announcement) detection may also be performed.

[0372] like Fig.21 As shown, the AP may send an R2R request frame to the non-AP STA1 identified during the SBP process establishment (i.e., a non-AP STA supporting R2R measurement) in order to perform R2R measurement. The non-AP STA1 receiving the R2R request frame from the AP may send an R2R response frame including information on whether to perform an R2R operation to the AP.

[0373] The RA field of the R2R request frame may be set to the ID of the non-AP STA that transmits a trigger frame to perform TF sounding in R2R measurement.

[0374] For example, the R2R request frame may include BW information, puncturing information, R2R non-AP STA information, R2R measurement establishment ID, and R2R measurement parameter information.

[0375] Here, the BW information refers to information about the BW used to perform R2R measurement. That is, the BW information may indicate the BW used for NDP transmission and reception.

[0376] The puncturing information may indicate information about a puncturing pattern within a BW. For example, the puncturing information may indicate whether puncturing is performed in units of 20 MHz or 40 MHz within a BW.

[0377] The R2R non-AP STA information may include information about the non-AP STA performing R2R measurement (e.g., information about Fig.21 Here, the information about the non-AP STA performing the R2R measurement may include AID information of the non-AP STA performing the R2R measurement (for example, ID information of the non-AP STA that sends the NDP for the R2R measurement), etc.

[0378] The non-AP STA 1 that initiates the R2R measurement may check information about other non-APs that perform the R2R measurement through the R2R non-AP STA information.

[0379] The R2R measurement setup ID may include identification information for R2R measurement. The R2R measurement setup ID may be used when requesting R2R measurement feedback. The R2R measurement setup ID may be set to a sensing measurement setup ID or an SBP setup ID.

[0380] The R2R measurement parameter information may include information on sensing parameters for performing R2R measurement. The sensing parameters for performing R2R measurement may include NSS, LTF type and CP, feedback type, and delayed feedback.

[0381] Here, NSS may represent information about the number of spatial streams used in NDP transmission. LTF type and CP may refer to configuration information of LTF symbols used in NDP transmission and CP size information. Feedback type may include feedback type information for R2R measurement. Delayed feedback may include information about whether delayed feedback is supported.

[0382] The R2R response frame may include response information of the R2R request frame. The response information may be sent via a status code.

[0383] For example, if the non-AP STA1 accepts the R2R response, the status code may be set to 'SUCCESS'. For example, if the non-AP STA1 rejects the R2R response, the status code may be set to 'R2R measurement rejection'.

[0384] As another example, if non-AP STA1 accepts the R2R response but wants to change the sensing parameters, the status code may be set to 'Preferred R2R Measurement Suggested'. When the status code is set to 'Preferred R2R Measurement Suggested', the R2R response frame may include information about the sensing parameters preferred by the non-AP STA.

[0385] A non-AP STA that has confirmed information on R2R measurement through the R2R request / response frame may transmit a trigger frame to another non-AP STA that performs R2R measurement (confirmed through the frame) to perform R2R measurement.

[0386] Here, the trigger frame may be defined as a (sub)variant of an R2R trigger frame which is a frame for initiating R2R measurement.

[0387] The TA of the trigger frame can be set to a non-AP STA that sends the trigger frame. Fig.21 , the TA of the trigger frame may be set to the address of the non-AP STA1, and the RA may be set to the address of the non-AP STA (ie, non-AP STA2) that receives the trigger frame and sends the NDP.

[0388] For example, the user (information) field of the trigger frame may include AID information, BW / allocation information, 'GI+LTF size (or / and type)' information, and NSS (number of spatial streams) information.

[0389] Here, the AID information may include ID information of a non-AP STA for transmitting an NDP for R2R measurement.

[0390] And, the BW / allocation information may include BW information for NDP transmission. The BW / allocation information may consist of the same 2 bits as the UL BW of the common information field of the trigger frame (i.e., bits indicating the BW in which the NDP is transmitted). The BW in which the NDP is transmitted may indicate one of 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 80+80 MHz.

[0391] As another example, the BW / allocation information may consist of 3 bits. In this case, the BW / allocation information may also indicate a BW of 320 MHz or higher as the BW on which the NDP is transmitted.

[0392] For example, the BW over which the NDP indicated by the BW / allocation information is transmitted may be configured to be less than or equal to the BW of the UL BW of the common information field of the trigger frame.

[0393] For example, the BW / allocation information included in the user information field in the corresponding trigger frame may include puncturing information. That is, the BW / allocation information may be configured with 5 bits to indicate the puncturing information. The non-AP STA may check the BW in which the NDP is transmitted through the UL BW subfield of the common information field of the corresponding trigger frame, and may check the information of puncturing within the BW through the BW / allocation information field.

[0394] The 'GI+LTF size (or / and type)' information may be used to indicate information about the GI and LTF sizes used when transmitting NDP. Specifically, the non-AP STA transmits NDP using the SU format and may check the GI and LTF sizes through the 'GI+LTF size (or / and type)' information.

[0395] Here, the 'GI+LTF size (or / and type)' information included in the user information field may be configured to be different from the 'GI+LTF type' information transmitted through the common information field of the corresponding trigger frame.

[0396] For example, the 'GI+LTF size (or / and type)' information may consist of 2 bits, as shown in Table 4 below.

[0397] [Table 4]

[0398] GI+LTF size subfield value Sensor Trigger Frame Variants 0 2x HE LTF+0.8us GI 1 2x HE LTF+1.6us GI 2 4x HE LTF+3.2us GI 3 Reserve

[0399] As another example of the present disclosure, when a trigger frame set to an SBP / R2R sensing trigger (sub) variant is sent, the 'GI+LTF size subfield' of the common information field of the trigger frame may be configured according to the above configuration (e.g., according to the configuration of Table 4, etc.). Then, the 'GI+LTF size subfield' of the common information field of the trigger frame may indicate information about the GI and LTF type (or / and size) of the NDP transmission using the SU format.

[0400] For example, if the common information field of the trigger frame includes the 'GI+LTF size subfield' configured as described above, the user information field of the trigger frame may not include the 'GI+LTF size subfield'.

[0401] The NSS information may indicate the number of spatial streams allocated when the NDP is transmitted. For example, the NSS information may consist of 3 bits and may indicate one of 1 to 8 as the number of spatial streams.

[0402] like Fig.21 As shown, non-AP STA2 receiving the trigger frame from non-AP STA1 can use the trigger frame information to send NDP to non-AP STA1. Non-AP STA1 can use the NDP received from non-AP STA2 to measure channel information between the two STAs.

[0403] The non-AP STA 1 may receive a feedback request frame from the AP. Here, the measured R2R measurement result may be sent to the AP.

[0404] like Fig.21 As shown, each frame may be sent at a SIFS interval, but various IFSs may be applied. For example, an IFS (eg, AIFS, DIFS, PIFS, etc.) with an interval greater than SIFS may be applied between a feedback request frame and a feedback report frame.

[0405] The above-mentioned embodiments are to combine the elements and features of the present disclosure in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be regarded as optional. Each element or feature can be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure may include a combination of some elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, the embodiments may include claims that do not have a clear reference relationship in the combined claims, or may be included as new claims by modification after application.

[0406] It is clear to those skilled in the relevant art that the present disclosure can be implemented in other specific forms within the scope of the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present disclosure should be determined by the reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0407] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in a device or computer according to the methods of various embodiments, and non-transitory computer-readable media that enable software or commands, etc. to be stored and executable in a device or computer. Commands that can be used to program a processing system that performs the features described in the present disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in the present disclosure can be implemented by using a computer program product that includes such a storage medium. The storage medium may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, but is not limited thereto, and it may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices located away from the processor. The memory, or alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system, and may be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results from the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0408] Industrial Applicability

[0409] The method proposed in the present disclosure is mainly described based on an example applied to a system based on IEEE 802.11 (5G system), but can be applied to various WLAN or wireless communication systems other than the system based on IEEE 802.11.

Claims

1. A method performed by a first station (STA) in a wireless LAN system, the method comprising: receiving, from the second STA, a sensing trigger frame including a sensing trigger subtype field, wherein the sensing trigger subtype field includes information indicating that the sensing trigger frame is a sensing responder to sensing responder SR2SR probe trigger frame; and In the SR2SR detection phase, based on the sensing trigger frame, a SR2SR null data physical protocol data unit PPDU NDP is sent to at least one STA or the SR2SR NDP is received from the at least one STA, The sensing trigger frame includes information indicating the role of the first STA in the SR2SR detection phase.

2. The method according to claim 1, wherein: The sensing trigger frame includes at least one of a single transmitter user information field and at least one receiver user information field, and The information indicating the role of the first STA is indicated by a transmit Tx / receive Rx subfield included in the single transmitter user information field or the at least one receiver user information field.

3. The method according to claim 2, wherein: The Tx / Rx field consists of 1 bit. The value of the Tx / Rx field included in the single transmitter user information field is set to 0, and A value of the Tx / Rx field included in the at least one receiver user information field is set to 1.

4. The method according to claim 2, wherein: Based on the role of the first STA being a SR2SR sensing transmitter, an association identity AID of the first STA is included in the single transmitter user information field.

5. The method according to claim 4, wherein: The sensing trigger frame including the at least one receiver user information field is sent to the at least one STA, and The at least one receiver user information field includes an AID of the at least one STA.

6. The method according to claim 2, wherein: The single transmitter user information field includes at least one of information about the number of spatial streams allocated to the first STA or the size of a long training field (LTF).

7. The method according to claim 1, wherein: The SR2SR field indicating information indicating support of SR2SR sounding is transmitted from the first STA to the second STA through a frame related to sensing measurement setup.

8. The method according to claim 4, wherein: Based on the SR2SR NDP being transmitted by at least one STA in a bandwidth of 160 MHz or less, sensing measurement through the SR2SR NDP is performed by the at least one STA.

9. The method according to claim 8, wherein: Based on requesting a frame for a sensing measurement result performed through the SR2SR NDP from the second STA to be transmitted to the at least one STA, a frame including the sensing measurement result is transmitted from the at least one STA to the second STA.

10. The method according to claim 1, wherein: A value of the sensing trigger subtype field included in the trigger dependency common information subfield of the sensing trigger frame is set to 4.

11. The method according to claim 1, wherein: The second STA is an SBP responder that has received an SBP request frame from a proxy sensing SBP initiator, and The SBP initiator is a non-access point AP STA, and the SBP responder is an AP.

12. The method according to claim 1, wherein: The SBP request frame includes parameters related to the SBP process and sensing measurements, and The SBP response frame sent by the SBP responder to the SBP initiator includes a status code for at least one of parameters related to the SBP process or the sensing measurement.

13. A first station STA in a wireless LAN system, the first STA comprising: at least one transceiver; as well as at least one processor connected to the at least one transceiver, Wherein, the at least one processor is configured to: receiving, by the at least one transceiver, a sensing trigger frame including a sensing trigger subtype field from a second STA, wherein the sensing trigger subtype field includes information indicating that the sensing trigger frame is a sensing responder to sensing responder (SR2SR) detection trigger frame; and In the SR2SR detection phase, a SR2SR null data physical protocol data unit PPDU NDP is sent to at least one STA through the at least one transceiver based on the sensing trigger frame, or the SR2SR NDP is received from the at least one STA through the at least one transceiver, The sensing trigger frame includes information indicating the role of the first STA in the SR2SR detection phase.

14. A method performed by a second station (STA) in a wireless LAN system, the method comprising: Sending a sensing trigger frame including a sensing trigger subtype field to a plurality of STAs including the first STA; as well as receiving, in a sensing responder to sensing responder SR2SR probing phase, a measurement result of a SR2SR null data physical protocol data unit PPDU NDP sent based on the sensing trigger frame from at least one STA among the plurality of STAs, The sensing trigger frame includes information indicating the role of the first STA in the SR2SR detection phase.

15. A second station STA in a wireless LAN system, the second STA comprising: at least one transceiver; as well as at least one processor connected to the at least one transceiver, Wherein, the at least one processor is configured to: transmitting, by the at least one transceiver, a sensing trigger frame including a sensing trigger subtype field to a plurality of STAs including the first STA; and receiving, through the at least one transceiver, a measurement result of a SR2SR null data physical protocol data unit PPDU NDP sent based on the sensing trigger frame from at least one STA among the plurality of STAs in a sensing responder to sensing responder SR2SR probing phase, The sensing trigger frame includes information indicating the role of the first STA in the SR2SR detection phase.

16. A processing device configured to control a first station STA in a wireless LAN system, the processing device comprising: at least one processor; as well as at least one computer memory operatively connected to the at least one processor and storing instructions that, upon execution by the at least one processor, perform operations comprising: receiving, from the second STA, a sensing trigger frame including a sensing trigger subtype field, wherein the sensing trigger subtype field includes information indicating that the sensing trigger frame is a sensing responder to sensing responder SR2SR probe trigger frame; and In the SR2SR detection phase, based on the sensing trigger frame, a SR2SR null data physical protocol data unit PPDU NDP is sent to at least one STA or the SR2SR NDP is received from the at least one STA, The sensing trigger frame includes information indicating the role of the first STA in the SR2SR detection phase.

17. At least one non-transitory computer-readable medium storing at least one instruction, in, The at least one instruction executable by at least one processor controls a device in a wireless LAN system: receiving, from the second STA, a sensing trigger frame including a sensing trigger subtype field, wherein the sensing trigger subtype field includes information indicating that the sensing trigger frame is a sensing responder to sensing responder SR2SR probe trigger frame; and In the SR2SR detection phase, based on the sensing trigger frame, a SR2SR null data physical protocol data unit PPDU NDP is sent to at least one STA or the SR2SR NDP is received from the at least one STA, The sensing trigger frame includes information indicating the role of the first STA in the SR2SR detection phase.

Images