Method for sensing in wireless local area network (WLAN)

Abstract

A method for wireless local area network (WLAN) sensing is provided herein. A method performed by a sensing responder may include receiving a first sensing measurement setting request message indicating a first one or more parameters to be used in a sensing measurement procedure. The method may include transmitting a first sensed measurement setting response message indicating at least one parameter different from the first one or more parameters indicated by the sensed measurement setting request message. The method may include receiving a second sensing measurement setting request message indicating a second one or more parameters to be used in the sensing measurement procedure. The second one or more parameters to be used in the sensing measurement procedure may include at least one parameter different from the first one or more parameters indicated by the first sensing measurement setting request message.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 335,061, filed on April 26, 2022, and U.S. Provisional Application No. 63 / 355,445, filed on June 24, 2022, the contents of which are incorporated herein by reference. Background Art

[0003] Wireless local area network (WLAN) sensing may enable a station (STA) to obtain sensing measurements of a channel between two or more STAs and / or a channel between a STA's receive antenna and transmit antenna. By performing WLAN sensing procedures, a STA may obtain sensing measurements useful for detecting and tracking environmental changes. Summary of the invention

[0004] A method for wireless local area network (WLAN) sensing is provided herein. The method performed by a sensing responder may include receiving a first sensing measurement setup request message, the first sensing measurement setup request message indicating a first one or more parameters to be used in a sensing measurement procedure. The method may include sending a first sensing measurement setup response message, the first sensing measurement setup response message indicating at least one parameter different from the first one or more parameters indicated by the sensing measurement setup request message. The method may include receiving a second sensing measurement setup request message, the second sensing measurement setup request message indicating a second one or more parameters to be used in the sensing measurement procedure. The second one or more parameters to be used in the sensing measurement procedure may include at least one parameter different from the first one or more parameters indicated by the first sensing measurement setup request message. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate similar elements, and in which:

[0006] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0007] Figure 1B is an example of an embodiment in which Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within the illustrated communication system;

[0008] Figure 1C is an example of an embodiment in which Figure 1A a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) used within the illustrated communication system;

[0009] Figure 1D is an example of an embodiment in which Figure 1A A system diagram of another example RAN and another example CN used within the illustrated communication system;

[0010] Figure 2 is an illustration of a number of examples including a trigger-based (TB) sensing measurement procedure that may use one of several different detection types;

[0011] Figure 3 Different examples of trigger-based measurement procedures are depicted;

[0012] Figure 4 An example format of a sensing measurement setup request frame is illustrated;

[0013] Figure 5 An example format of a sensing measurement setup response frame is illustrated;

[0014] Figure 6 An example format of a sensed measurement parameter element is illustrated;

[0015] Figure 7 Examples of elements that may be included in an action frame or element such as Figure 6 Examples of sensory measurement parameter fields in the illustrated sensory measurement parameter element;

[0016] Figure 8 An example format of a sensing measurement setup termination frame is illustrated;

[0017] Fig. 9 illustrates an example format of an SBP request frame;

[0018] Fig.10 illustrates an example format of an SBP response frame;

[0019] Fig.11 An example of a trigger frame format is illustrated;

[0020] Fig.12 illustrates an example format of the Extreme High Throughput (EHT) variant User Information field;

[0021] Fig.13 An example format of the EHT Special User Information field is illustrated;

[0022] Fig.14 is a table illustrating an example encoding of a trigger type subfield included in a common information subfield of a trigger frame;

[0023] Fig.15 An example format of the trigger-related common information subfield of the ranging trigger frame is illustrated;

[0024] Fig.16 is a table illustrating example encodings of the trigger-related common information subfield of the ranging trigger frame variant;

[0025] Fig.17 Another example format of the trigger-related common information subfield of the ranging trigger frame is illustrated;

[0026] Fig.18 illustrates an example format of a trigger-related user information field in a ranging trigger frame that may be included for polling and reporting sub-variant frames;

[0027] Fig.19 and Fig. 20 The example formats of the trigger-related user information field in the detection sub-variant and the safety detection sub-variant of the ranging trigger frame are respectively illustrated;

[0028] Fig.21 illustrates an example encoding of an NDP announcement variant frame;

[0029] Fig. 22 An example of the NDPA notification frame format is illustrated;

[0030] Fig.23 An example of the STA Information field for the EHT NDPA variant is illustrated;

[0031] Fig.24 An example format of the Special STA Information field when the value of the AID11 subfield is less than 2008 is illustrated;

[0032] Fig.25 An example format of the Special STA Information field when the value of the AID11 subfield is 2043 is illustrated;

[0033] Fig.26 An example format of the Special STA Information field when the value of the AID11 subfield is 2044 is illustrated;

[0034] Fig. 27 An example format of the Special STA Information field when the value of the AID11 subfield is 2045 is illustrated;

[0035] Fig.28 illustrates an example format of an EHT operation element;

[0036] Fig.29 illustrates an example format of the EHT Operation Information field;

[0037] Fig.30 An example WLAN sensing procedure for TB measurement setup negotiation is illustrated;

[0038] Fig.31An exemplary WLAN sensing procedure for TB measurement setup negotiation is illustrated, wherein an alternative response is received from a sensing responder;

[0039] Fig.32 Another example WLAN sensing procedure for TB measurement setup negotiation is illustrated;

[0040] Fig.32 An exemplary sensing procedure for TB measurement setup negotiation between a sensing initiator and multiple sensing responders, wherein the multiple responders indicate different responses in a measurement setup request frame, is depicted;

[0041] Fig.33 An example sensing procedure for TB measurement setup negotiation between a sensing initiator and a plurality of sensing responders, wherein all of the responders accept sensing measurement parameters indicated in a measurement setup request frame, is illustrated;

[0042] Fig.34 An example sensing procedure for TB measurement setup negotiation performed between a sensing initiator and a plurality of sensing responders, wherein all of the responders reject sensing measurement parameters indicated in a measurement setup request frame;

[0043] Fig.35 An example of a non-TB measurement setup negotiation procedure performed between a sensing initiator (non-AP STA) and a sensing responder (AP) is illustrated;

[0044] Fig.36 An example of a non-TB measurement setup negotiation procedure involving a sensing initiator (e.g., a non-AP STA) and a sensing responder (e.g., an AP) is illustrated;

[0045] Fig.37 is an illustration of an exemplary non-TB measurement setup negotiation procedure involving a sensing initiator (e.g., a non-AP STA) and a sensing responder (e.g., an AP);

[0046] Fig.38 is another illustration of an exemplary non-TB measurement setup negotiation procedure involving a sensing initiator (e.g., a non-AP STA) and a sensing responder (e.g., an AP);

[0047] Fig.39 is a table illustrating an exemplary encoding of the Status Code subfield in a Sensing Measurement Setup Response frame;

[0048] Fig.40 A non-TB measurement example is illustrated, where the initiator (e.g., non-AP STA0) is the sensing transmitter, and the AP and other non-AP STAs (e.g., non-AP STA1, non-AP STA2) are the sensing receivers;

[0049] Fig.41 A non-TB measurement example is illustrated, where the initiator (e.g., non-AP STA0) and other non-AP STAs are sensing receivers, and the sensing responder (i.e., AP) is the sensing transmitter;

[0050] Fig.42 An example of a non-TB measurement instance is illustrated, where the sensing initiator (e.g., non-AP STA0 and other non-AP STAs) is the sensing transmitter, and the AP is the sensing receiver;

[0051] Fig.43 illustrates an exemplary frame exchange between a non-AP STA initiating multiple simultaneous non-TB sensing measurement instances and different APs in a multi-AP group;

[0052] Fig.44 An exemplary SBP procedure involving multiple SBP initiators is illustrated. Fig.44 In the example shown, the SBP initiator 4420 (i.e., non-AP STA0) may first transmit an SBP request to the SBP responder 4410 (i.e., the AP);

[0053] Fig.45 An exemplary SBP procedure involving a single SBP initiator and a set of SBP participants is illustrated. The set of SBP participants includes a plurality of SBP participants;

[0054] Fig.46 An example of a procedure for termination of sensing measurements initiated by an AP is illustrated, where the AP may be a sensing initiator;

[0055] Fig.47 illustrates an example of an exemplary measurement setup ID information subfield in a sensing measurement setup termination frame action field;

[0056] Fig.48 An exemplary sensing measurement setup termination procedure initiated by a non-AP STA is illustrated; and

[0057] Fig.49 The timing requirements for each phase of a sensing TB measurement instance are illustrated. DETAILED DESCRIPTION

[0058] Figure 1A1 is a diagram illustrating an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word discrete Fourier transform spread OFDM (ZT-UW-DFT-S-OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0059] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (CN) 106, a public switched telephone network (PSTN) 108, the Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a station (STA)) may be configured to send and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0060] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B such as a gNode B (gNB), a new radio (NR) Node B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0061] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to send and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrums. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to send and / or receive signals in a desired spatial direction.

[0062] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0063] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), that may use Wideband CDMA (WCDMA) to establish the air interface 116. WCDMA may include communication protocols, such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​Uplink (UL) Packet Access (HSUPA).

[0064] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro).

[0065] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology (such as NR radio access) that may establish the air interface 116 using NR.

[0066] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may together implement LTE radio access and NR radio access, for example using the dual connectivity (DC) principle. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).

[0067] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0068] Figure 1A The base station 114b in the may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial venues, homes, vehicles, campuses, industrial facilities, sky corridors (e.g., for use by drones), roads, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not be required to access the Internet 110 via the CN 106.

[0069] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 may provide call control, billing services, mobile location-based services, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the accompanying drawings, the CN 106 may be configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1AAlthough not shown in the figure, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may utilize NR radio technology, the CN 106 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0070] The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired communication networks and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0071] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0072] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0073] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0074] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from the base station via an air interface 116. For example, in one embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to send and / or receive, for example, IR, UV or visible light signals. In another embodiment, the send / receive element 122 may be configured to send and / or receive both RF signals and optical signals. It should be understood that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.

[0075] Although the transmit / receive element 122 Figure 1B 1 as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0076] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0077] The processor 118 of the WTRU 102 may be coupled to and may receive user input data from a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0078] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0079] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0080] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripheral device 138 may include one or more sensors. The sensor may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geographic location sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor, etc.

[0081] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (e.g., for transmission) and DL (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via signal processing performed by hardware (e.g., a choke) or via a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (e.g., for transmission) or DL ​​(e.g., for reception)) may be concurrent and / or simultaneous.

[0082] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0083] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0084] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0085] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. Although the foregoing elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0086] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0087] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0088] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0089] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers.

[0090] Although the WTRU Figures 1A to 1D Although described as wireless terminals, it is contemplated that in certain representative embodiments, such terminals may (eg, temporarily or permanently) use a wired communication interface with a communication network.

[0091] In a representative embodiment, the other network 112 may be a WLAN.

[0092] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STA) associated with the AP. The AP may have access or an interface to a distributed system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and leading to the STA may be reached by the AP and may be delivered to the STA. Traffic originating from the STA and leading to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be transmitted by the AP, for example, wherein the source STA may transmit traffic to the AP, and the AP may deliver traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be transmitted between the source STA and the destination STA (e.g., directly between them) using a direct link setup (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs within or using the IBSS (eg, all STAs in the STA) may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad hoc" communication mode.

[0093] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may send beacons on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may listen to the primary channel. If the primary channel is listened / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0094] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0095] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz channels and / or 80MHz channels can be formed by combining continuous 20MHz channels. 160MHz channels can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be sent by the transmitter STA. At the receiver of the receiver STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be transmitted to the medium access control (MAC).

[0096] 802.11af and 802.11ah support operating modes below 1GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0097] WLAN systems that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) a 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (which only supports a 1MHz operating mode) is transmitting to the AP, all available bands may be considered busy even if most of the available bands remain idle.

[0098] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0099] Figure 1D1 is a system diagram illustrating the RAN 104 and the CN 106 in accordance with an embodiment. As noted above, the RAN 104 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0100] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to send signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to send wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, gNB 180a may transmit multiple component carriers to WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum, while the remaining component carriers may be on licensed spectrum. In an embodiment, gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0101] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with parameter sets that may be scalable. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0102] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRU 102a, 102b, 102c may communicate / connect with the gNB 180a, 180b, 180c while also communicating / connecting with another RAN, such as the evolved Node-B 160a, 160b, 160c. For example, the WTRU 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more evolved Node-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the evolved Node-B 160a, 160b, 160c may act as a mobility anchor for the WTRU 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRU 102a, 102b, 102c.

[0103] Each of the gNBs 180a, 180b, 180c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, interworking between DC, NR, and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0104] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0105] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N2 interface and may act as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of non-access stratum (NAS) signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services utilized by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, etc. The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies, such as WiFi.

[0106] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 106 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 106 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0107] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via the N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, etc.

[0108] The CN 106 may facilitate communications with other networks. For example, the CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired networks and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to the DNs 185a, 185b via the UPFs 184a, 184b via the N3 interfaces to the UPFs 184a, 184b and the N6 interfaces between the UPFs 184a, 184b and the local DNs 185a, 185b.

[0109] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following items may be performed by one or more simulation devices (not shown): WTRU102a to 102d, base station 114a to 114b, evolved Node B 160a to 160c, MME 162, SGW 164, PGW 166, gNB180a to 180c, AMF 182a to 182b, UPF 184a to 184b, SMF 183a to 183b, DN 185a to 185b and / or any other device described herein. The simulation device may be one or more devices configured to mimic one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0110] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or in an operator network environment. For example, one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. One or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for the purpose of testing and / or performing tests using over-the-air wireless communications.

[0111] One or more simulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device can be used in a test scenario in a test laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. One or more simulation devices can be test equipment. Direct RF coupling and / or wireless communication via an RF circuit system (e.g., which can include one or more antennas) can be used by the simulation device to send and / or receive data.

[0112] This article describes an overview of a WLAN system. A WLAN in infrastructure basic service set (BSS) mode may include an access point (AP) for the BSS and one or more stations (STA), which may include non-AP-STA and / or AP-STA. One or more STAs may be associated with an AP. The AP may access or interface with a distributed system (DS) or other types of wired / wireless networks that carry traffic in and out of the BSS. Traffic originating from outside the BSS and directed to the STA may be reached through the AP and may be delivered to the STA. Traffic originating from the STA and directed to a destination outside the BSS may be transmitted to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may also be transmitted through the AP. For example, a source STA may transmit traffic to an AP, and the AP may deliver traffic to one or more destination STAs.

[0113] When using, for example, the 802.11ac infrastructure operating mode, the AP may use a fixed channel (which may be referred to as the primary channel) to send beacons. The primary channel may be 20 MHz wide and may be considered an operating channel for the BSS. The primary channel may also be used by STAs to establish connections with one or more APs. The basic channel access mechanism in 802.11 systems is carrier sense multiple access / collision avoidance (CSMA / CA). In this operating mode, each STA including the AP may sense the primary channel. If the channel is detected to be busy, the STA may back off. Therefore, one STA may transmit at any given time in a given BSS.

[0114] For example, in an 802.11n compliant operation mode, a high throughput (HT) STA may also communicate using a 40 MHz wide channel. This may be achieved by combining a primary 20 MHz channel with an adjacent 20 MHz channel to form a 40 MHz wide contiguous channel.

[0115] For example, in an operation mode that complies with 802.11ac, a very high throughput (VHT) STA may support 20MHz, 40MHz, 80MHz, and 160MHz wide channels. 40MHz and 80MHz channels may be formed by combining continuous 20MHz channels similar to the above-mentioned 802.11n. For example, a 160MHz channel may be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (which may also be referred to as an 80+80 configuration). For an 80+80 configuration, after channel coding, data is passed through a segment parser that divides the data into two streams. An inverse discrete Fourier transform (IDFT) operation and time domain processing are performed separately on each stream. These streams are then mapped onto two channels, and data may be sent. At the receiver, the mechanism may be reversed, and the combined data may be transmitted to the MAC.

[0116] To improve spectral efficiency, for example, an 802.11ac compliant operating mode may support downlink multi-user MIMO (MU-MIMO) transmissions to multiple STAs within a time frame of the same symbol (e.g., during a downlink OFDM symbol). The possibility of using downlink MU-MIMO is also considered for the 802.11ah operating mode. It is important to note that since downlink MU-MIMO can use the same symbol timing for multiple STAs when it is used in 802.11ac and other standards, interference from waveform transmissions to multiple STAs is not a problem. However, the STAs involved in MU-MIMO transmissions with the AP may need to use the same channel or frequency band, and this may limit the operating bandwidth to the minimum channel bandwidth supported by the STAs involved in MU-MIMO transmissions with the AP.

[0117] This article provides an overview of the Extremely High Throughput implementation and 802.11be. The IEEE 802.11 Extremely High Throughput (EHT) study group was established in September 2018. EHT can be considered as the major revision to the IEEE 802.11 standard after 802.11ax. EHT explores the possibility of further increasing the peak throughput and improving the efficiency of IEEE 802.11 networks. Following the establishment of the EHT study group, the 802.11be task group was established to deliver the 802.11EHT specification. The use cases and applications addressed may include high throughput and low latency applications such as video over WLAN, augmented reality (AR), and virtual reality (VR).

[0118] The list of features that have been discussed in conjunction with EHT and 802.11be to achieve the goals of increased peak throughput and improved efficiency includes at least: multi-AP coordination, multi-band / multi-link, 320 MHz bandwidth, 16 spatial streams, HARQ, and a new design for 6 GHz channel access.

[0119] This article provides an introduction to 802.11bf. The IEEE 802.11bf standard is considered to be a modification of IEEE 802.11 regarding wireless sensing capabilities in WLAN. The task of the new task group TGbf is to generate specification documents. One or more of the following principles may be reflected in the standard. A sensing procedure may allow a STA to perform WLAN sensing and obtain measurement results. A sensing session may be considered as an instance of a sensing procedure, which has associated operating parameters of the instance. A sensing initiator may be a STA that initiates a WLAN sensing session. A sensing responder may be a STA that participates in a WLAN sensing session initiated by a sensing initiator. A sensing transmitter may be a STA that sends a PPDU for sensing measurements in a sensing session. A sensing receiver may be a STA that receives a PPDU transmitted by a sensing transmitter and performs sensing measurements in a sensing session. A STA may assume multiple roles in a sensing session. In a sensing session, a sensing initiator may be a sensing transmitter, a sensing receiver, both, or neither.

[0120] WLAN sensing is further described in detail herein. WLAN sensing may enable a STA (e.g., a non-AP STA or an AP-STA) to obtain sensing measurements of a channel used for communication between two or more STAs and / or a channel between a receiving antenna and a transmitting antenna of a STA. By performing WLAN sensing procedures, it is possible for a STA to obtain sensing measurements useful for detecting and tracking environmental changes.

[0121] Figure 2is an illustration of several examples of a trigger-based (TB) sensing measurement procedure that may use one of several different detection types. Figure 2 As shown, the TB sensing measurement sensing procedure may involve at least one sensing initiator (eg, AP 210) and at least one sensing responder (eg, non-AP STA 220). Figure 2 The illustrated illustration may depict signaling exchanges between the initiator 210 and the responder 220 at the medium access control (MAC) layer or the physical (PHY) layer, and between higher layer entities implemented within the initiator 210 and the responder 220. Figure 2 As shown, the sensing initiator 210 has a station management entity 211 and a MAC layer management entity (MLME) 212. Similarly, the sensing responder 220 has an MLME 221 and an SME 222. The SMEs 211 and 222 are responsible for generating primitives, and the MLME 212 and MLME 221 construct frames (e.g., a sensing measurement setup request frame, a sensing measurement setup response frame, etc.) according to the primitives.

[0122] like Figure 2 As shown, when the MLME-SESTBMSMTRQ.request primitive is generated by SME 211, the sensing initiator 201 may be configured to initiate a null data packet announcement (NDPA) probe and / or a trigger frame (TF) probe. When the MLME-SENSMSMTTERMINATION.request primitive is generated by SME 211 or by SME213, the sensing initiator 201 and / or the sensing responder 202 may be configured to terminate the sensing measurement setup. The NDPA and TF probe procedures and the sensing measurement setup termination procedure are further described in detail in the following paragraphs. It should be understood that Figure 2 The illustrations are examples of basic procedures and are not an exhaustive illustration of all possible uses of the protocol.

[0123] The format of a sensing measurement setup request frame is described herein. The sensing measurement setup request frame may be sent, for example, by a sensing initiator to request a sensing measurement setup.

[0124] Figure 3Different examples of trigger-based measurement procedures are depicted. As shown in each of examples 310, 320, 330, 340, and 350, a trigger-based measurement instance may be initiated by a polling phase (which may include sending or receiving one or more polling frames). As shown in example 310, the polling phase is followed by a short interframe space (SIFS), followed by an NDPA detection phase. As further illustrated in example 310, the detection phase may be followed by a SIFS, followed by a reporting phase. Example 320 is similar to example 310, with at least one difference being that the NDPA detection phase is replaced by a TF detection phase. As shown in examples 330 and 340, a measurement instance may include both an NDPA detection phase and a TF detection phase, and such phases may be performed in different orders. As shown in example 350, two measurement instances may be performed. In the depicted scenario, the reporting phase may be delayed and may be performed in another TB measurement instance.

[0125] In the following paragraphs, detailed information on the format of the sensing measurement setup request frame is provided.The sensing measurement setup response frame may be sent by a sensing responder, for example, in response to a sensing measurement setup request frame.

[0126] Figure 4 An example format of a sensing measurement setup request frame is illustrated. The format of the sensing measurement setup request frame may define fields of an action frame. Figure 4 As shown, the sensing measurement setting request frame 400 may include a measurement setting ID field and / or a sensing measurement parameter element. The measurement setting ID field may include information indicating a measurement setting ID, which identifies the assigned parameters in the sensing measurement parameter element to be used in the corresponding sensing measurement instance. The sensing measurement parameter element may be further defined, for example, in the subsequent paragraphs of this document.

[0127] Figure 5 An example format of a sensing measurement setup response frame is illustrated. The format of the sensing measurement setup response frame may define the fields of the action frame. Figure 5As shown, the sensing measurement setup response frame 500 may include a status code field and / or a sensing measurement parameter element. The status code field may indicate a response to one or more parameters, fields, or elements, for example, included in the sensing measurement setup request frame. For example, the value indicated by the status code field may indicate that the request is successful, the request is declined, and / or the request is rejected. Depending on the value of the status code, the sensing measurement parameter element may be present in the sensing measurement setup response frame. For example, the sensing measurement parameter element present in the sensing measurement setup response frame may include one or more recommended parameters (e.g., PREFERRED_MEASURMENT_SETUP_PARAMETERS_SUGGESTED) to be used in the sensing procedure. In some cases, the sensing measurement parameter element may not be present in the sensing measurement setup response frame. The sensing measurement parameter element may be further defined in subsequent paragraphs of this document.

[0128] The sensing measurement parameters element is described in greater detail herein.The sensing measurement parameters element may include information indicating operational properties of the corresponding sensing measurement instance.

[0129] Figure 6 An example format of a sensor measurement parameter element is shown. Figure 6 As shown, the sensing measurement parameter element 600 may include an element ID field, a length field and / or a sensing measurement parameter field. Figure 7 The sensing measurement parameter fields are described in further detail.

[0130] Figure 7 Examples of elements that may be included in an action frame or element such as Figure 6 Examples of sensing measurement parameter fields in the sensing measurement parameter element illustrated and described above. Figure 7 As shown, the sensing measurement parameter field 700 may include, for example, a sensing transmitter subfield, a sensing receiver subfield, a measurement report type subfield, and / or one or more other subfields. The sensing transmitter subfield and the sensing receiver subfield may indicate one or more identifiers of STAs assigned the roles of the sensing transmitter and the sensing receiver, respectively.

[0131] The sensing measurement setup termination frame format is described herein. The sensing measurement setup termination frame may be used to terminate one or more sensing measurement setups. The sensing measurement setup termination frame may be sent by a non-AP STA or an AP-STA (e.g., by a sensing initiator or a sensing responder). The sensing measurement setup termination frame may be sent to one or more participants in a sensing measurement setup procedure.

[0132] Figure 8 An example format of a sensing measurement setup termination frame is illustrated. The format of the sensing measurement setup termination frame may define the fields of the action frame. Figure 8As shown, the sensing measurement setup termination frame 800 includes at least measurement setup ID information. The measurement setup ID information indicates, for example, an identifier associated with a setup instance to be terminated.

[0133] Methods and procedures for proxy-based sensing (SBP) are described herein. SBP enables a STA (e.g., a non-AP STA or AP-STA) to obtain sensing measurements of a channel, such as between an AP and one or more STAs (e.g., non-AP STAs), between multiple non-AP STAs, or between a receiving antenna and a transmitting antenna of an AP. By executing the SBP procedure, it is possible for a STA (e.g., a non-AP STA or AP-STA) to obtain sensing measurements required for detecting and tracking environmental changes. In some scenarios, when dot11SBPImplemented is true, a non-AP STA may act as an SBP initiator; and, for example, when dot11SBPImplemented is true, an AP may act as an SBP responder. Those skilled in the art will appreciate that in other scenarios, an AP-STA may also act as an SBP initiator, and a non-AP STA may also act as an SBP responder.

[0134] SBP procedure setup is described herein. To establish an SBP procedure, an SBP initiator may transmit an SBP request frame to an AP with SBP responder capability. Upon receiving the SBP request frame, the SBP responder may, for example: accept the SBP procedure request, in which case the SBP responder may transmit an SBP response frame with a status code of SUCCESS; or reject the SBP procedure request, in which case the SBP responder may transmit a frame (e.g., an SBP response frame) with a status code indicating that the request is rejected (e.g., with a code of REQUEST_REJECTED).

[0135] In response to the SBP request frame, the SBP responder may send a frame (e.g., an SBP response frame) within a given time period. If no SBP response frame is received within the time period, or if an SBP response frame with a status code equal to REQUEST_REJECTED is received, the SBP procedure setup may be terminated. For example, if one or both of the SBP initiator or the SBP responder determines that the time period has passed (e.g., since the SBP response frame was sent), one or both of the SBP initiator or the SBP responder may terminate the SBP procedure setup. The time period may be a configurable parameter at the SBP responder and / or at the SBP initiator.

[0136] An SBP responder that transmits an SBP response frame with a status code of SUCCESS may initiate a WLAN sensing procedure with one or more non-APSTAs. The SBP responder may initiate a WLAN sensing procedure using an operating parameter derived from an operating parameter indicated in an SBP request frame requesting the SBP procedure. The SBP responder may be a sensing initiator of the WLAN sensing procedure. The SBP initiator may participate in the WLAN sensing procedure as a sensing responder.

[0137] The SBP request frame format is described in more detail herein. As described above, the SBP request frame may be sent by an SBP initiator, which may be an AP-STA or a non-AP STA. The format of the SBP request frame may define the fields of the action frame. The SBP request frame may allow or enable a STA to invoke an SBP procedure.

[0138] Fig. 9 An example format of an SBP request frame is shown. Fig. 9 As shown, the SBP request frame 900 may include at least a dialog token field, which may be set to a non-zero value selected by the STA transmitting the SBP request. The dialog token field may, for example, include information identifying a request / response transaction.

[0139] The SBP response frame format is described herein. The SBP response frame may be sent by a STA (e.g., by an AP-STA or a non-AP STA) to accept or reject a request for an SBP procedure, such as a request received via an SBP request frame substantially as described in the above paragraphs. The format of the SBP response frame may define the fields of the action frame. Fig.10 The format of the SBP response frame action field is described in further detail.

[0140] Fig.10 An example format of an SBP response frame is shown. Fig.10 As shown, the SBP response frame 1000 may include a dialogue token field. The dialogue token field may be set to the same value as the dialogue token field of the corresponding SBP request frame. If the STA (e.g., AP-STA or non-AP STA) sending the SBP response frame accepts the request, the status code may indicate such success of the request. Otherwise, if the AP STA rejects the request, the status code may indicate this (e.g., the status code may be set to REQUEST_REJECTED (with a given number of octets)).

[0141] like Fig.10As shown, the SBP response frame 1000 may include a measurement setup ID field. The measurement setup ID field may be set to a measurement setup ID value corresponding to a measurement setup instance initiated by the AP that accepts the corresponding SBP request. For example, if the status code indicates or is equal to SUCCESS, the measurement setup ID field may be present in the SBP response frame.

[0142] Various aspects of trigger frames are discussed herein. The trigger frames may be implemented in a manner consistent with one or more modifications of the 802.11 specification (e.g., using the High Efficiency (HE) trigger frame format as set forth in 802.11ax) to allocate resources and trigger single-user or multi-user access in the uplink.

[0143] Fig.11 An example of the trigger frame format is shown. Fig.11 As shown, the trigger frame 1100 includes, for example, a MAC header (e.g., including a duration field, a receiving address (RA) field, and a transmitting address (TA) field), a common information field, and a user information list field. The common information field includes, for example, a trigger type subfield indicating a variant of the trigger frame, a more TF subfield, a CS required subfield, and other types of subfields.

[0144] In systems implemented according to the 802.11be modification, new variations of the trigger frame format (e.g., an extremely high throughput (EHT) enhanced trigger frame) may be used. For example, according to some formats, new variations of the user information field may be utilized, and a special user information field may be added along with the common information field.

[0145] Fig.12 and Fig.13 An example format of the EHT variant user information field and an example format of the EHT special user information field are respectively illustrated. Fig.12 and Fig.13 Both illustrate enhancements that may allow, prompt, or enable a unified triggering scheme for both HE and EHT devices. Fig.12 and Fig.13 As shown, the EHT variant user information field 1200 and the EHT special user information field 1300 may each include a trigger-related user information field, which may include a trigger type subfield indicating a sub-variant of the trigger frame. The trigger-related user information field is further described in detail in the following paragraphs.

[0146] Fig.14is a table of example encodings of the trigger type subfield included in the common information subfield of the illustrated trigger frame. The trigger frame variant value sent by the signal may indicate a basic trigger frame, a beamforming report poll (BFRP) trigger frame, a multi-user block ACK report (MU-BAR) trigger frame, a multi-user request transmission (MU-RTS) trigger frame, a buffer status report poll (BSRP) trigger frame, a multicast with retry (GCR) MU-MAR trigger frame variant, a bandwidth query report poll (BQRP) trigger frame, an NDP feedback report poll (NFRP) trigger frame, or a ranging trigger frame variant. A ranging trigger variant may be an example of a trigger frame variant having one or more sub-variants defined. About Fig.16 The ranging trigger variants and potential sub-variants are described in further detail.The ranging trigger subtype field value in the trigger-related common information field of the ranging trigger frame is also described further in the following paragraphs.

[0147] Fig.15 An example format of the trigger-related common information subfield of the ranging trigger frame is illustrated. The token field in the trigger-related common information field 1500 can be used in the ranging trigger frame, for example, the polling sub-variant frame. The token field can, for example, match the token field associated with the partial time synchronization function (TSF) time in the subsequent ranging NDP announcement frame. The bit used to indicate the token can be reserved in other ranging trigger sub-variants.

[0148] Fig.16 is a table illustrating an example encoding of the trigger-related common information subfield of the ranging trigger frame variant. Fig.16 As shown, the ranging trigger subtype may be encoded using different values ​​for each of the sub-variants of polling, probing, safety probing, reporting, and passive TB probing.

[0149] Fig.17 Another example format of the trigger-related common information subfield of the ranging trigger frame is illustrated. Fig.17 The ranging trigger frame 1700 shown may be a sub-variant for passive TB detection. The Probe Dialogue Token Number subfield may contain a value in the range of 0 to 63, which may identify a measurement probe phase (e.g., an Initiator to Responder Null Data Packet (I2R NDP) and a Responder to Initiator Null Data Packet (R2I NDP) announced by a Probe Trigger Frame and a Ranging NDP Announcement Frame, respectively), and the same value may be included in the Probe Dialogue Token field of a Ranging NDP Announcement Frame sent within the same availability window.

[0150] Except that the RA field in the ranging trigger frame including only one user information field can indicate a unicast address or a broadcast address, the RA field in the common information field of the ranging trigger frame variant and the required CS subfield and UL BW subfield can be the same as those of the basic trigger frame variant.

[0151] The More TF subfield of the Common Information field of the ranging trigger frame may be set to 1, and the RA field may be set to the broadcast address to indicate that a subsequent ranging trigger frame of the polling sub-variant is scheduled for transmission within the availability window. The More TF subfield of the Common Information field of the ranging trigger frame may be set to 0, and the RA field may be set to the broadcast address to indicate that no subsequent ranging trigger frame of the polling sub-variant is scheduled for transmission within the availability window.

[0152] For example, if the trigger frame is addressed only to the initiator STA (ISTA), the TA field for the ranging trigger frame can be set to the address of the responder STA (RSTA) that sent the trigger frame, and the RSTA is performing a TB ranging measurement exchange with the initiator STA. If the trigger frame is addressed to a set of ISTAs, where at least two ISTAs are performing a TB ranging measurement exchange with different BSSIDs in the RSTA's multi-BSSID set, the TA field can be the sent BSSID.

[0153] Fig.18 An example format of the trigger-related user information field in the ranging trigger frame is illustrated, which example format may be included for the polling and reporting sub-variant frames. Fig.18 As shown, the trigger-related user information subfield 1800 may not be present in the polling sub-variant or the reporting sub-variant of the ranging trigger frame.

[0154] Fig.19 and Fig. 20 The example formats of the trigger-related user information field in the detection sub-variant and the safety detection sub-variant of the ranging trigger frame are respectively illustrated. The trigger-related user information field may not exist in the detection sub-variant of the ranging trigger frame. Fig.19As shown, for example, the AID12 / RSID12 subfield of the trigger-related user information fields 1900 and 2000 may carry 12 LSBs of the AID for the associated ISTA or 12 LSBs of the RSID for the unassociated ISTA. The UL target RSSI subfield may be the same as the corresponding subfield in the basic trigger frame. The AID12 / RSID12 subfield may be the same as the corresponding subfield in the polling subvariant of the ranging trigger frame. The I2R Rep subfield may signal the number of repetitions N_REP of the HE LTF symbol in the corresponding HE TB ranging NDP from the STA indicated in the AID12 / RSID12 subfield. The value of the I2R Rep subfield may be the same in all user information fields in the trigger frame. The SS allocation and UL target RSSI subfields may be the same as the corresponding subfields in the basic trigger frame.

[0155] like Fig. 20 As shown, for example, the AID12 / RSID12 subfield may be the same as the corresponding subfield in the polling subvariant of the ranging trigger frame. The I2R Rep subfield may signal the number of repetitions N_REP of the HE LTF symbol in the corresponding HE TB ranging NDP from the STA indicated in the AID12 / RSID12 subfield. The SS allocation and UL target RSSI subfields may be the same as the corresponding subfields in the basic trigger frame. The trigger-related user information subfield may be present in the Fig. 20 In the depicted secure detection sub-variant of the ranging trigger frame. The trigger-related user information subfield may carry a secure authentication code (SAC) field. The SAC field may provide authentication information for LTF sequence generation information for I2R detection associated with the measurement instance. The length of this subfield may be 16 bits.

[0156] The passive TB ranging sub-variant of the ranging trigger frame may follow the definitions for the sounding sub-variant of the ranging trigger frame, except that the RA field may always be set to the broadcast address and the I2R Rep subfield may signal the number of repetitions N_REP of the HE LTF symbol in the corresponding HE ranging NDP from the STA indicated in the AID12 / RSID12 subfield.

[0157] The sending of an NDPA frame may initiate a detection or sensing procedure based on NDPA. For example, NDPA may notify participants (i.e., non-AP STAs and / or AP-STAs) of the NDP PPDU to be sent and the detection or sensing procedure to be started. NDPA may also include detection or sensing requirements. The sensing transmitter may then send an NDP PPDU that has no payload but includes LTF symbols that enable participants to measure the wireless channel. Participants may then report their corresponding channel measurement results using the methods described in further detail herein. This article describes NDPA variants. In a system implemented according to the 802.11 specification, there may be Fig.21 Four variations of NDPA are listed.

[0158] Fig.21 An example encoding of an NDP announcement variant frame is shown. Fig.21 As shown, the NDPA type subfield included in the NDP announcement frame may indicate that the NDP announcement frame is a VHT NDP announcement frame, a ranging NDP announcement frame, a HE NDP announcement frame, or an EHT NDP announcement frame.

[0159] Fig. 22 An example of the NDP announcement frame format is shown. Fig. 22 As shown, the NDP announcement frame may include a MAC header (e.g., including a duration field, an RA field, and a TA field), a detection dialogue token, and one or more STA information fields. Those skilled in the art will understand that Fig. 22 The example format of the NDP announcement frame shown may be applicable to, for example, a HE NDP announcement frame, a ranging NDP announcement frame, and / or an EHT NDP announcement frame.

[0160] Fig.23 An example of the STA Information field of the EHT NDPA variant is illustrated. Figure 24 to Figure 27 The example format of the Special STA Information field of the HE Ranging NDP Announcement frame variant is illustrated. Specifically, Fig.24 An example format of the Special STA Information field when the value of the AID11 subfield is less than 2008 is illustrated. Fig.25 An example format of the Special STA Information field when the value of the AID11 subfield is 2043 is illustrated. Fig.26 An example format of the Special STA Information field when the value of the AID11 subfield is 2044 is illustrated. Fig. 27 An example format of the Special STA Information field when the value of the AID11 subfield is 2045 is illustrated.

[0161] Preamble puncturing is a feature that can be implemented in a manner consistent with, for example, 802.11ax to allow STAs to transmit on certain subchannels rather than the entire bandwidth. In other words, the punctured transmission of the PPDU may not have a signal in one or more subchannels within the PPDU bandwidth. In 802.11be, two types of preamble puncturing schemes are defined, namely static puncturing and dynamic puncturing.

[0162] With static puncturing, one or more subchannels may be punctured for one or more beacon intervals. The AP may include a field such as a Disabled Subchannel Bitmap field in the EHT Operation element to indicate that one or more subchannels are disabled. The STA may set the TXVECTOR parameter INACTIVE_SUBCHANNELS of the HE, EHT, or non-HT repeat PPDU based on the value indicated in the Disabled Subchannel Bitmap field previously exchanged (e.g., most recently exchanged) in the EHT Operation element for the BSS. The STA may not send anything on the disabled subchannels.

[0163] Fig.28 An example format of an EHT operation element is shown. Fig.28 As shown, the EHT operation element 2800 includes an element ID field, a length field, an element ID extension field, an EHT operation information field, and / or a disabled sub-channel bitmap (eg, as described above). When present, the disabled sub-channel bitmap may be, for example, 2 octets long.

[0164] Fig.29 The example format of the EHT Operation Information field is shown in FIG. The EHT Operation Information field may include: Fig.29 The subfields shown include a channel width subfield, a CCFS subfield that defines the channel center frequency band information, and / or a disabled subchannel bitmap subfield, which can indicate whether the disabled subchannel bitmap field exists in the EHT operation element. The encoding of the channel width subfield can indicate, for example, whether the EHT BSS bandwidth is 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz.

[0165] The valid puncturing pattern may be defined in a manner consistent with the 802.11 standard. However, with dynamic puncturing, a STA may be allowed to puncture additional subchannels in addition to the subchannels indicated by the Disabled Subchannel Bitmap field. A STA may determine to puncture additional subchannels for different reasons. For example, such puncturing may be based on its physical or virtual channel sensing results. For example, the U-SIG field in the EHT MU PPDU may be used to explicitly signal dynamic puncturing. The Perforated Channel Information field may be carried in the U-SIG field of the EHT MU PPDU to indicate the perforated channel.

[0166] The various problems to be solved by the solution proposed in this article can be described as follows. Some problems may involve procedures for sensing role negotiation. In a TB measurement instance or a non-TB measurement instance, the sensing initiator may not know the complete status of the sensing responder. Due to the availability (or unavailability) of the sensing responder, such as channel availability, data buffer status, power availability, etc., the sensing responder may not be able to act as the sensing role assigned or suggested by the sensing initiator. Therefore, it may be necessary to define a set of procedures for sensing role negotiation, which allows the sensing responder to suggest its sensing role in a TB measurement instance or a non-TB measurement instance.

[0167] Some issues may involve enhanced procedures for non-TB measurement instances with multiple STAs. When compliant with the 802.11bf specification, non-TB sensing measurement instances may be considered in pairs, i.e., a non-AP STA may be an initiator and an AP may be a sensing responder. A sensing initiator (or sensing responder) may be a sensing transmitter, a sensing receiver, or both. In some scenarios, other non-AP STAs (which may not be sensing initiators) may want to participate in the sensing measurement instance. For example, an AP may want to transmit an NDP to multiple non-AP STAs, which may include a sensing initiator. Alternatively or additionally, when an AP is a sensing receiver, it may want to receive an NDP from multiple non-AP STAs, which may include a sensing initiator. However, there may be no defined procedures to indicate how multiple non-AP STAs (not sensing initiators) may participate in non-TB measurement instances. Therefore, it may be necessary to define an efficient procedure to reduce the signaling overhead and signaling time when multiple non-AP STAs (not sensing initiators) participate in non-TB measurement instances.

[0168] Some issues may involve SBP procedures with multiple SBP requesters. When compliant with the 802.11bf specification, Proxy-Based Sensing (SBP) is a procedure that may allow or enable a non-AP STA to request an AP to perform WLAN sensing on its behalf. There may be scenarios where more than one non-AP STA wants to request an AP to perform WLAN sensing on its behalf. There may not be a defined procedure to enable multiple non-AP STAs to request an AP to perform SBP simultaneously.

[0169] Some issues may involve enhanced procedures for sensing measurement termination with multiple STAs. When compliant with the 802.11bf specification, the sensing measurement termination procedure may not be defined, especially considering that when multiple STAs have the same sensing measurement ID (e.g., serving the same application), there may not be a clear specification on how to efficiently terminate these STAs. Therefore, it may be necessary to define an efficient sensing measurement termination procedure for multiple STAs to reduce the sensing signaling overhead.

[0170] Some issues may involve procedures for estimating the number of participating sensing responders per TXOP. In the existing 802.11bf specification, each TB sensing measurement instance may be limited by the duration of the TXOP. The TB sensing measurement instance may include one or more stages in each of the following stages: a polling stage, an NDPA detection stage, a TF detection stage, and / or a reporting stage. As the number of sensing responders increases, the TB sensing measurement instance may include multiple polling stages, multiple TF detection stages, multiple NDPA detection stages, and / or multiple reporting stages. The number of stages that can be accommodated in a TXOP may be limited by the duration of the TXOP. Given the duration of a TXOP, a calculation procedure may be required to estimate the number of stages, and therefore estimate the number of responders that may participate in a TB measurement instance.

[0171] Various solutions are provided herein that address at least some of the problems described in the above paragraphs. Some embodiments may relate to procedures for sensing role negotiation. The TB sensing measurement setup negotiation procedure may be a subset of such procedures.

[0172] Some scenarios addressed may involve a sensing initiator (AP) negotiating with a sensing responder (non-AP STA). In one such scenario, the AP (which may be the sensing initiator) may transmit a sensing measurement setup request to a non-AP STA acting as a sensing responder. The measurement setup procedure may allow or enable negotiation between the sensing initiator (AP) and the sensing responder (non-AP STA).

[0173] Fig.30 An example WLAN sensing procedure for TB measurement setup negotiation is illustrated. Fig.30 As shown, the sensing initiator 3001 (eg, AP-STA, such as Fig.30 ) performs communication with the sensing responder 3002 (eg, a non-AP STA, such as Fig.30The sensing initiator 3001 may transmit a sensing measurement setup termination frame 3030 to terminate the sensing measurement setup procedure. The sensing responder 3002 may transmit an ACK as shown at 3040 to confirm the receipt of the sensing measurement setup termination frame 3030.

[0174] Fig.31 An exemplary WLAN sensing procedure for TB measurement setup negotiation is illustrated, wherein an alternative response is received from a sensing responder. Fig.31 As shown, the sensing initiator 3101 (eg, AP-STA) sends a sensing measurement setup request frame 3110 to at least the sensing responder 3102 (eg, non-APSTA), similar to the above description of Fig.30 Upon receiving the sensing measurement setup request frame 3110, the sensing responder 3102 may not accept the assigned sensing role indicated in the sensing measurement setup request frame 3110. The sensing responder 3102 may send a sensing measurement setup response frame 3120 to the sensing initiator 3101. The sensing measurement setup response frame 3120 may include a field or value indicating "alternative". In addition, as Fig.31 As shown, the sensing responder 3102 may also include a set of recommended parameters in the sensing measurement setup response frame 3120, for example, the sensing role that the sensing responder preferably plays in the sensing measurement instance. Upon receiving the sensing measurement setup response frame 3120 from the sensing responder 3102, the sensing initiator 3101 may again send a sensing measurement setup request frame (shown at 3130 in this example) to indicate new sensing measurement parameters. The sensing responder 3102 may again transmit a sensing measurement setup response frame (shown at 3140) with a field or value indicating "accept". Alternatively or additionally, the sensing responder may repeat the negotiation process and transmit a sensing measurement setup response with "replace" or "reject". When the sensing responder 3102 sends (or when the sensing initiator 3101 receives) the sensing measurement setup response frame 3140 with an "accept" indication, the sensing measurement instance may begin, as shown at 3150.

[0175] If the sensing responder transmits another sensing measurement setup response frame including an "alternative" indication, the sensing initiator may need to confirm the alternative sensing measurement parameters suggested by the sensing responder. For example, the sensing initiator may transmit the sensing measurement setup request again. The system may limit the number of sensing measurement setup request frames sent from the sensing initiator. For example, the maximum number of sensing measurement setup request frames sent may be set equal to 2. The system may limit the number of sensing measurement setup response frames sent from the sensing responder. For example, the maximum number of sensing measurement setup response frames sent (e.g., the maximum number of sensing measurement response frames sent including an "alternative" indication) may be set equal to 2. In some cases, the system may limit the negotiation duration between the sensing initiator and the sensing responder, for example, by configuring a timer. When the duration expires, the sensing measurement setup may be terminated, or the sensing responder may start the sensing measurement instance using the sensing measurement parameters indicated in the latest sensing measurement setup request frame, or the sensing initiator may start the sensing measurement instance using the alternative sensing measurement parameters indicated in the latest sensing measurement setup response frame.

[0176] Some scenarios may involve one sensing initiator (e.g., AP-STA or non-AP-STA) transmitting a sensing measurement setup request to multiple sensing responders (e.g., non-AP STA or AP-STA). For example, in some scenarios of such scenarios, an AP acting as a sensing initiator may transmit a sensing measurement setup request to a group of non-AP STAs that also act as sensing responders. In such measurement setup procedures, this may allow negotiation between a sensing initiator (e.g., AP) and multiple sensing responders (e.g., non-AP STAs). These sensing responders may belong to the same group, which may be indicated by a group ID in various messaging.

[0177] Fig.32 An exemplary sensing procedure for TB measurement setup negotiation between a sensing initiator and multiple sensing responders is depicted, wherein the multiple responders indicate different responses in a measurement setup request frame. Fig.32 As shown, the sensing initiator AP 3201 may transmit a sensing measurement setup request frame to multiple sensing responders (e.g., non-AP STAs 3202, 3203, and 3204). The sensing measurement setup trigger frame may be sent by the sensing initiator 3201 SIFS after the sensing measurement setup request frame. RU allocations for sending multiple sensing measurement setup response frames from multiple STAs may be included in the trigger frame. Upon receiving the sensing measurement setup trigger frame, the requested STAs 3202, 3203, and 3204, which may belong to a group of sensing responders, each transmit a sensing measurement setup response frame using the RU allocation indicated by the trigger frame. The sensing responders 3202, 3203, and 3204 may indicate different responses. As shown in FIG. Fig.32As shown, the sensing responder 3202 (STA1) may transmit a sensing measurement setup response frame indicating "acceptance"; the sensing responder 3203 (STA2) may transmit a sensing measurement setup response frame indicating "rejection"; and the sensing responder 3204 (STA3) may transmit a sensing measurement setup response frame indicating "replacement". After receiving the sensing measurement setup response frames from multiple responders, the sensing initiator 3201 may take different actions with respect to each sensing responder: the sensing initiator may transmit a sensing measurement termination frame to the sensing responder 3203 (STA2), which may reply with an ACK. This may mean that the sensing measurement setup between the APs has not been completed. The sensing initiator 3201 may transmit a sensing measurement setup request frame to the sensing initiator 3204, which includes an alternative sensing setup parameter suggested by the sensing responder 3204 (STA3). Upon receiving the new sensing measurement setup request frame, the sensing responder 3204 may transmit a sensing measurement setup response with an indication of "acceptance" to the sensing initiator 3201. After exchanging all these frames, the sensing measurement setup is successfully completed between the sensing initiator 3201 and the sensing responders 3202 and 3204. The sensing measurement setup procedure may not be completed between the sensing initiator 3201 and 3203. For the sensing initiator (e.g., AP), this may involve which sensing responder (e.g., STA) should be contacted first after receiving the sensing measurement setup response frame from multiple sensing responders.

[0178] Fig.33 An example sensing procedure for TB measurement setup negotiation between a sensing initiator and a plurality of sensing responders is illustrated, wherein all of the responders accept the sensing measurement parameters indicated in a measurement setup request frame. Fig.33 As shown, the sensing initiator AP 3301 may transmit a sensing measurement setup request frame to a plurality of sensing responders (e.g., non-AP STAs 3302, 3303, and 3304). Once the sensing initiator 3301 receives the sensing measurement setup response frame (e.g., from each of the sensing responders 3302, 3303, and 3324), the sensing initiator 3301 may start a sensing measurement instance, as shown at 3310.

[0179] Fig.34 An example sensing procedure for TB measurement setup negotiation performed between a sensing initiator and a plurality of sensing responders is illustrated, wherein all of the responders reject the sensing measurement parameters indicated in the measurement setup request frame. Fig.34As shown, the sensing initiator AP 3401 may transmit a sensing measurement setup request frame to multiple sensing responders (e.g., non-AP STAs 3402, 3403, and 3404). In such an example, after receiving a sensing measurement response frame indicating "rejection" from all sensing responders, the sensing initiator 3401 may transmit a sensing measurement termination frame to all responders, which may be followed by a trigger frame (e.g., a sensing measurement setup trigger frame). The sensing measurement termination frame may be sent after a subframe in SIFS. The sensing responders 3402, 3403, and 3404 may transmit ACK, for example, SIFS after receiving the trigger frame.

[0180] This document describes a non-TB sensing measurement setup negotiation procedure. In a non-TB sensing measurement instance, a non-AP STA may be a sensing initiator and an AP may be a sensing responder. Before the sensing measurement instance begins, the sensing measurement parameters indicated in the sensing measurement request frame between the sensing initiator (non-AP STA) and the sensing responder (AP) are negotiated. The sensing responder AP may accept, reject, replace, or require the sensing measurement parameters indicated in the sensing measurement request frame.

[0181] Fig.35 An example of a non-TB measurement setup negotiation procedure performed between a sensing initiator (non-AP STA) and a sensing responder (AP) is illustrated. Fig.35 In the example shown, the sensing initiator 3501 may send a sensing measurement setup request frame 3510 to the sensing responder 3502. The sensing responder 3502 may indicate "reject" in a sensing measurement setup response frame 3520. In other words, the sensing responder 3502 may not accept the sensing measurement parameters indicated in the sensing measurement setup request frame 3510, and may not provide any alternative parameters. Once the sensing initiator 3501 has received the sensing measurement setup response 3520 including the "reject" indication, the sensing initiator 3501 may terminate the sensing measurement setup, i.e., by outgoing a sensing measurement setup termination frame 3530, which may be followed by an ACK 3540 from the sensing responder 3510.

[0182] Fig.36 An example of a non-TB measurement setup negotiation procedure involving a sensing initiator (eg, a non-AP STA) and a sensing responder (eg, an AP) is illustrated. Fig.36In the example shown, the sensing initiator 3601 may send a sensing measurement setup request frame 3610 to the sensing responder 3602. The sensing responder 3602 may indicate "alternative" in a sensing measurement setup response frame 3620. In the sensing measurement setup response frame 3620, the responder 3602 may include alternative sensing measurement parameters. The sensing initiator 3601 may accept these parameters and implement these parameters or include these parameters in a subsequent sensing measurement setup request frame 3630, which may be transmitted to the responder 3602. Alternatively or additionally, the indication of the "alternative" value in the sensing measurement setup response frame 3620 may allow, prompt or enable another negotiation process between the sensing initiator 3601 and the sensing responder 3602. The system may limit the number of negotiations, such as a maximum number of negotiations, which may be equal to the maximum number of transmissions of the sensing measurement request frame (equal to 2). Alternatively or additionally, the system may set a timer to limit the negotiation duration. When the timer expires, in some cases, the sensing measurement setup may terminate; or in some cases, the sensing responder 3602 may implement or accept the sensing measurement parameters indicated in the most recent sensing measurement setup request frame to start the sensing measurement instance. In some cases, the sensing initiator 3601 may implement or accept the alternative sensing measurement parameters indicated in the most recent sensing measurement setup response frame to start the sensing measurement instance.

[0183] Fig.37 An exemplary non-TB measurement setup negotiation procedure involving a sensing initiator (eg, a non-AP STA) and a sensing responder (eg, an AP) is illustrated. Fig.37 As shown, the sensing initiator 3701 may send a sensing measurement setup request frame 3710 to the sensing responder 3702. The sensing responder may send a sensing measurement setup response frame 3720 and include a value indicating "required". The sensing measurement setup response frame 3720 may include an indication of parameters different from the parameters included in the sensing measurement setup request frame 3710. "Required" may indicate that the sensing responder may only accept the sensing parameters indicated in the sensing measurement setup response frame 3720. For example, if the sensing initiator 3601 accepts or agrees to the required sensing parameters, the sensing initiator 3701 may transmit a subsequent sensing measurement setup request frame 3730, which may include the required sensing parameters. Fig.37 As shown, the sensing responder 3702 may send a subsequent sensing measurement setup response 3740 including an indication that the setup procedure was successful and accepting values ​​for the parameters indicated in the subsequent sensing measurement setup request 3730. As shown at 3750, a sensing measurement instance may then begin.

[0184] Fig.37Another exemplary non-TB measurement setup negotiation procedure involving a sensing initiator (eg, a non-AP STA) and a sensing responder (eg, an AP) is illustrated. Fig.38 As shown, the sensing initiator 3801 may send a sensing measurement setup request frame 3810 to the sensing responder 3802. The sensing responder may send a sensing measurement setup response frame 3820 and include a value indicating "required". The sensing measurement setup response frame 3820 may include an indication of parameters that are different from the parameters included in the sensing measurement setup request frame 3810. If the sensing initiator 3801 does not agree to the required sensing parameters, the sensing initiator may terminate the sensing measurement setup by sending a sensing measurement setup termination message, as shown at 3830. The sensing responder 3802 may send an ACK in response to the sensing initiator 3801.

[0185] This document describes a solution involving a sensing measurement setup response frame. This document further discusses the sensing measurement setup response frame action field format.

[0186] Fig.39 is a table illustrating exemplary encodings of a status code subfield in a sensing measurement setup response frame. The status code subfield may include information indicating, for example, "success", "reject", "alternative", "required", or other values. The status code subfield may include, for example, an indication of partial acceptance of parameters included in the sensing measurement setup request frame. For example, partial acceptance may occur when a participant (e.g., a sender of a sensing measurement setup response frame) accepts some or a portion of the parameters indicated in the sensing measurement setup request frame.

[0187] It should be noted that the sensing role may change from one sensing measurement instance to another sensing measurement instance. Therefore, a sensing role negotiation procedure may be required in each sensing measurement setup.

[0188] Embodiments related to enhanced procedures for non-TB measurement instances involving multiple STAs are described herein. In a non-TB measurement instance, for example, where a non-AP STA is a sensing initiator and an AP is a sensing responder, other non-AP STAs may be enabled to participate in the sensing measurement instance. A non-AP STA may be a sensing transmitter, a sensing receiver, or both.

[0189] Fig.40 A non-TB measurement example is illustrated, in which the initiator (e.g., non-AP STA0) is the sensing transmitter, and the AP and other non-AP STAs (e.g., non-AP STA1, non-AP STA2) are sensing receivers. Fig.40In the example shown, the sensing initiator 4010 (i.e., non-AP STA0) may transmit a sensing measurement setup request frame. The sensing responder 4020 (i.e., AP) may send a sensing measurement setup response frame to the sensing initiator 4010 as a response. In the sensing measurement setup response frame, the sensing responder 4020 may indicate that it accepts all sensing measurement parameters in the sensing measurement parameters indicated in the sensing measurement setup request frame sent by the sensing initiator 4010. The sensing responder 4020 (AP) may indicate in the response frame that its associated STAs (e.g., non-AP STA 4030 (STA1) and non-AP STA 4040 (STA2)) agree to participate in the sensing measurement setup. Upon receiving the sensing measurement setup response frame with a success indication, the sensing initiator (i.e., non-AP STA0) may send an NDP announcement (NDPA) frame, which may be followed by one or more NDPs. For example, the one or more NDPs may be sent, for example, SIFS after the NDPA. At SIFS after sending the NDP, the sensing responder (i.e., AP) may send a trigger frame to the non-AP STA 4030 (i.e., STA1) and the non-AP STA 4040 (i.e., STA2), which may indicate resource allocation information for sending a sensing measurement report frame by the non-AP STA 4030 and the non-AP STA 4040. At SIFS after the trigger frame, the sensing responder 4020, the non-AP STA 4030, and the non-AP STA 4040 may transmit a sensing measurement response frame, which may be received by the sensing initiator 4010 (i.e., non-AP STA0). The sensing result may be carried in the sensing measurement report frame.

[0190] Fig.41 A non-TB measurement example is illustrated, in which the initiator (eg, non-AP STA0) and other non-AP STAs are sensing receivers, and the sensing responder (ie, AP) is the sensing transmitter. Fig.41In the example shown, the sensing initiator 4110 (i.e., non-AP STA0) transmits a sensing measurement setup request frame. The sensing measurement setup response frame is followed by a sensing measurement setup response frame from the sensing responder 4120 (i.e., AP). In the sensing measurement setup response frame, the sensing responder may indicate that it accepts all sensing measurement parameters included in the sensing measurement setup request frame sent by the sensing initiator 4110. The sensing responder 4120 (AP) may indicate in the response frame that its associated STAs (e.g., non-AP STA 4130 (STA1) and non-AP STA 4140 (STA2)) agree to participate in the sensing measurement setup. Upon receiving the sensing measurement setup response frame with a success indication, the sensing initiator may send an NDP announcement (NDPA) frame, followed by an NDP after a SIFS. The NDP may be sent, for example, by the sensing responder 4120 (i.e., AP). SIFS after the NDP, the sensing responder 4120 may transmit a trigger frame to other participants 4110, 4130, and 4140 (i.e., to non-AP STA0, non-AP STA1, and non-AP STA2), and indicate resource allocation information for a sensing measurement report frame to be sent by the other participants 4110, 4130, and 4140 (i.e., non-AP STA0, non-AP STA1, and non-AP STA2). SIFS after the trigger frame, the sensing initiator 4110 (i.e., non-AP STA0), non-AP STAs 4130 and 4140 (i.e., STA1 and STA2) may transmit a sensing measurement report frame, which may be received by the sensing responder 4120 (i.e., AP). The sensing result may be carried in the sensing measurement report frame ( Fig.41 (not shown).

[0191] Fig.42 An example of a non-TB measurement instance is illustrated, in which the sensing initiator (eg, non-AP STA0 and other non-AP STAs) is the sensing transmitter, and the AP is the sensing receiver. Fig.42As shown, the sensing initiator 4210 (i.e., non-AP STA0) may transmit a sensing measurement setup request frame, which may be followed by a sensing measurement setup response frame sent by the sensing responder 4220 (i.e., AP). In the sensing measurement setup response frame, the sensing responder 4220 may indicate that it accepts all sensing measurement parameters indicated in the sensing measurement setup request frame sent by the sensing initiator 4210 (i.e., non-AP STA0). The sensing responder 4220 (AP) may indicate in the response frame that its associated STAs (e.g., non-AP STA 4230 (STA1) and non-AP STA 4240 (STA2)) agree to participate in the sensing measurement setup. Upon receiving the sensing measurement setup response frame including the acceptance indication, the non-AP STA0 may send an NDP announcement (NDPA) frame, which may be followed by a trigger frame sent by the sensing responder 4220 (i.e., AP) after SIFS. The trigger frame may be transmitted to other participants 4210, 4230, and 4240 (i.e., non-AP STA0, non-AP STA1, and non-AP STA2), and may indicate resource allocation information for sending a sensing measurement report frame by the participants 4210, 4230, and / or 4240 (i.e., non-AP STA0, non-AP STA1, and / or non-AP STA2). SIFS after the trigger frame, the sensing responder (i.e., the AP) may transmit a sensing measurement report frame that may be received by the participants 4210, 4230, and / or 4240 (i.e., non-AP STA0, non-AP STA1, and / or non-AP STA2). The sensing result may be carried in the sensing measurement report frame ( Fig.42 (not shown).

[0192] In order to enable participants (i.e., non-AP STA1 and non-AP STA2) to participate in the sensing measurement instance initiated by the sensing initiator (i.e., non-AP STA0) and to transmit the sensing results to the sensing initiator and / or the sensing responder (i.e., non-AP STA0 or AP), one or more optional procedures may be adopted. In some cases, the NDPA may be transmitted by the sensing initiator (i.e., non-AP STA0), which may include STA information of the participants (i.e., non-AP-STA1 and non-AP-STA2), and indicate whether such participants are sensing receivers or / and sensing transmitters and which device is the sensing transmitter. For example, in Fig.40 In the example shown, non-AP STA0 may be a sensing transmitter; Fig.41 In the example shown, the AP can be a sensing transmitter. Fig.42 In the example shown, non-AP STA0, non-AP STA1, and non-AP STA2 may be sensing transmitters.

[0193] In some options, non-AP STAs may be grouped. For example, if any non-AP STA or group head non-AP STA from the same group acts as a sensing initiator and sends an NDPA, the remaining non-AP STAs in the group may perform as sensing receivers or transmitters and transmit sensing results to the sensing transmitter if necessary (for example, non-AP STA0 may be Fig.40 The sensing transmitter in the example shown, the AP may be Fig.41 The sensing transmitter in the example shown, and non-AP STA0, non-AP STA1 and non-AP STA2 may be as shown in FIG. Fig.42 One or more group IDs may be included in the NDPA and / or trigger frame. In some cases, an indication of a group head may be included in the NDPA and / or trigger frame.

[0194] This document describes a simultaneous non-TB sensing measurement instance in a multi-AP scenario. In some embodiments, a non-AP STA may initiate a non-TB sensing measurement instance with one or more APs in a multi-AP scenario, so that the non-AP STA may be a sensing initiator and the APs in the multi-AP group may be sensing responders participating in the sensing session. The foregoing scenario may be described in the following paragraphs about Fig.43 Examples are further illustrated and described.

[0195] Fig.43 An exemplary frame exchange between a non-AP STA initiating multiple simultaneous non-TB sensing measurement instances and different APs in a multi-AP group is illustrated. Fig.43 As shown, the sensing initiator 4310 is a non-AP STA, and the sensing responders 4320, 4330, and 4340 are APs (i.e., AP1, AP2, and AP3). The sensing initiator 4310 sends a sensing NDPA frame, which is followed by an I2R NDP PPDU sent after a SIFS. Subsequently, after another SIFS, the sensing responders 4320, 4330, and 4340 send R2I NDP PPDUs in response.

[0196] In some embodiments, the non-AP STA may be a sensing transmitter, and some or all APs in the multi-AP group participating in the sensing session may be sensing receivers. In some methods, the non-AP STA may transmit a sensing NDPA with a STA information field addressed to the group AID or special AID to provide configuration information for the I2R NDP, which may be transmitted by the non-AP SIFS after the NDPA. Some or all APs in the multi-AP group may then transmit R2INDP SIFS after the I2R NDP. The sensing NDPA may be used to configure the R2I NDP to be sent with the minimum possible length using one LTF. In some methods, the non-AP STA may transmit a sensing NDPA with many STA information fields, and each STA information field may be addressed to one AP in the multi-AP group participating in the sensing session. In each STA information field, the configuration of the R2I NDP may be the same or different. In some methods, the non-AP STA may configure one AP to transmit the R2I NDP, while other APs in the multi-AP group may remain silent and not respond with the R2I NDP. The AP transmitting the R2I NDP may be a shared AP in a multi-AP group, or it may be an associated AP of a non-AP STA initiating a sensing session.

[0197] In some embodiments, a non-AP STA may be a sensing receiver, and all APs participating in a sensing session in a multi-AP group may be sensing transmitters. A non-AP STA may transmit a sensing NDPA, which is followed by an I2R NDP transmitted after a SIFS, and an AP in a multi-AP group may transmit an R2I NDP after a SIFS. In some methods, a non-AP STA may transmit a sensing NDPA with a STA information field addressed by a group AID or a special AID. The STA information field may be used to configure an I2R NDP that will be sent with a minimum possible length using an LTF. The sensing NDPA may also be used to configure the transmission of R2I NDPs from different APs in a multi-AP group participating in a sensing session. When a unique STA information field is used, the AP may respond by transmitting an R2I NDP with the same configuration indicated in the STA information field. In some methods, the unique STA information field may be used to allocate different resources to different APs to transmit the R2I NDPA. In some methods, a non-AP STA may transmit a sensing NDPA with many STA information fields, and each STA information field may be addressed to one of the APs participating in the sensing session in the multi-AP group. The STA information field may be used to configure R2I NDPs sent from different APs with different configurations. These R2I NDPs may then be transmitted in a time domain, frequency domain, or spatial domain multiplexing form or in any combination of these three domains. These R2I NDPs may also be transmitted in a non-orthogonal manner using the same time domain, frequency domain, and spatial domain.

[0198] In some embodiments, a non-AP STA may be a sensing transmitter and receiver, and some of the APs participating in the sensing session in a multi-AP group are sensing transmitters, and some APs are only sensing receivers. The non-AP STA may transmit a sensing NDPA, which is followed by an I2R NDP transmitted after SIFS, and the APs in the multi-AP group may then transmit an R2INDP after SIFS. In one method, the non-AP STA may transmit a sensing NDPA with two STA information fields, each STA information field is addressed with a group AID or a special AID, so that one STA information field is used for the AP sensing transmitter, and one STA information field is used for the AP sensing receiver. The AP sensing transmitter STA information field can be used to configure the R2INDP to be sent from the AP acting as a sensing transmitter. The AP sensing receiver STA information field can be used to configure the I2R NDP to be sent from the non-AP STA to the AP acting as a sensing receiver. In some methods, the non-AP STA may transmit a sensing NDPA with many STA information fields, and each STA information field may be addressed to one of the APs participating in the sensing session in the multi-AP group. The STA Information field can be used to configure R2I NDPs sent from different APs acting as sensing transmitters with different configurations. These R2I NDPs can then be transmitted in a time domain, frequency domain, or spatial domain multiplexed form or in any combination of these three domains. These R2I NDPs can also be transmitted in a non-orthogonal manner using the same time domain, frequency domain, and spatial domain. In addition, the STA Information field can be used to configure I2R NDPs sent from non-AP STAs to different APs acting as sensing receivers.

[0199] In some embodiments, when a non-AP STA acts as both a sensing transmitter and a receiver, the I2R NDP and the R2INDP may be used to perform measurements in both directions, such that the non-AP STA may use the R2I NDP to obtain CSI for a link between itself and an AP acting as a sensing transmitter or as a sensing transmitter and receiver, and the AP acting as both a sensing transmitter and a receiver may use the I2RNDP to obtain CSI for a link between itself and the non-AP STA.

[0200] Embodiments related to SBP procedures involving multiple SBP requests are described herein. In the SBP procedure, a non-AP STA may be enabled or prompted to obtain sensing measurements of a channel between an AP and one or more non-AP STAs. In such cases, there may be a scenario in which multiple non-AP STAs may transmit SBR requests to an AP during a time interval T_out, which may be defined by the system. In such a scenario, an enhanced procedure is proposed that prompts or enables the AP to transmit one or more SBP responses to these SBP initiators simultaneously or continuously. These methods may improve signaling efficiency and reduce overhead.

[0201] Fig.44 An exemplary SBP procedure involving multiple SBP initiators is illustrated. Fig.44 In the example shown, the SBP initiator 4420 (i.e., non-AP STA0) may first transmit an SBP request to the SBP responder 4410 (i.e., AP). The SBP request may be followed by a SIFS, followed by an SBP response from the SBP responder 4410. A timer may start running (i.e., the SBP responder 4410 may determine when a duration has elapsed from when the sensing responder 4410 received the first SBP request). Before T_out expires, or before the duration has elapsed, the SBP responder 4410 may receive another SBP request from the SBP initiator 4430 (i.e., non-AP STA1). After the SBP request and SBP response message exchange is performed between the SBP initiator 4430 and the SBP responder 4410 and the time from the counting start point is less than T_out, the SBP responder 4410 may receive another SBP request from the SBP initiator 4440. After the SBP responder 4410 transmits the SBP response frame to the SBP initiator 4440, the elapsed duration may reach T_out. All three SBP initiators may belong to the same group or request similar content, for example, using the same application or the same CSI information associated with similar or the same channel. The SBP responder 4410 may decide to initiate a single sensing procedure for these SBP initiators at the same time. The SBP responder 4410 may terminate the SBP procedure, i.e., transmit an SBP termination request to one or more of the three SBP initiators 4420, 4430 and / or 4440 at any time simultaneously or non-simultaneously. A time interval or duration (e.g., T_out) may be used to limit a duration during which SBP requests from STAs of the same SBP group are received, and these SBP requests may be merged into one SBP procedure. Alternatively or additionally, any one of the SBP initiators may terminate the SBP procedure.

[0202] In some embodiments, a non-AP STA may transmit an SBP request frame to an AP, which may be an SBP responder. Upon receiving the SBP request, the SBP responder may recognize that the SBP initiator belongs to a group of non-AP STAs and decide to transmit another SBP response frame to other non-AP STAs that belong to the same group as the SBP initiator.

[0203] Fig.45 An exemplary SBP procedure involving a single SBP initiator and a set of SBP participants including a plurality of SBP participants is illustrated. Fig.45In the example shown, the SBP initiator 4520 (i.e., non-AP STA0) may include its group ID in the SBP request frame. Upon receiving the SBP request from the SBP initiator 4520, the SBP responder 4510 (i.e., AP) may identify the group ID and decide to transmit another SBP request to the non-AP STA 4530 (i.e., STA1) and the non-AP STA 4540 (i.e., STA2), the other SBP request may indicate that the sensing procedure may start at a time interval T, which may start at the end of the reception of the SBP response. For example, T may be equal to aSIFTime+aSlotTime+aRxPHYStartDelay. Once the group of non-AP STAs joins the SBP procedure, the requirements set by the SBP initiator (e.g., sensing measurement and / or reporting requirements) may be applied to all group members or active group members. For example, in this case, the required sensing measurement results may be transmitted to the non-AP STA 4520 and / or the non-AP STA 4530 and / or the non-AP STA 4540. The SBP responder 4510 may terminate the SBP procedure by transmitting an SBP termination request frame. In this example, the SBP initiator 4520 (i.e., non-AP STA0) may indicate any of the following information in the SBP request frame: 1) SBP group ID; and / or 2) information that group members, a portion of group members, or all group members are not allowed to participate in the SBP procedure. If the SBP initiator 4520 (i.e., non-AP STA0) does not allow any other non-AP STA to participate in the SBP procedure, the SBP responder 4510 (i.e., AP) may not transmit an SBP response frame to other group members. If the SBP initiator 4520 (i.e., non-AP STA0) only allows a portion of group members to participate in the SBP procedure, the SBP responder 4510 (i.e., AP) may transmit an SBP response frame only to those group members that are allowed to join the SBP procedure. If the SBP initiator 4520 (i.e., non-AP STA0) allows all group members to participate in the SBP procedure, the SBP responder 4510 (i.e., AP) may transmit an SBP response frame to all group members of non-AP STA0. In this example, the SBP initiator 4520 (i.e., non-AP STA0) may initiate the SBP termination procedure. The SBP responder 4510 may first transmit an SBP termination response frame to the non-AP STA 4520, and then transmit separate frames to the non-AP STA 4530 (non-AP STA1) and the non-AP STA 4540 (non-AP STA2). Alternatively, the SBP responder 4510 may transmit one SBP termination response frame to the non-AP STA 4520, the non-AP STA 4530, and the non-AP STA 4540.Alternatively or additionally, the SBP responder 4510 (ie, AP) may terminate the SBP procedure; or if other group members are participating in the SBP procedure, the other group members may terminate the SBP procedure.

[0204] Embodiments related to sensing measurement termination involving multiple STAs are described herein. Sensing measurement termination initiated by an AP may be performed as described in the following paragraphs. In some embodiments, a sensing measurement termination procedure involving an AP and multiple non-AP STAs may be proposed. In such a procedure, the AP may be a sensing initiator and initiates termination of sensing measurements.

[0205] Fig.46 An example of a procedure for termination of sensing measurements initiated by an AP is illustrated, where the AP may be the sensing initiator. Fig.46 As shown, the sensing initiator 4610 (i.e., AP) may transmit a sensing measurement setup termination frame to the sensing responders 4620, 4630, and 4640 (i.e., one or more intended STAs). A period of time (e.g., SIFS) after receiving the sensing measurement setup termination frame, the sensing responders 4620, 4630, and 4640 indicated as recipients of the sensing measurement setup termination frame may transmit an ACK or a sensing measurement setup termination response frame to the sensing initiator 4610. After the ACK or response frame, the sensing initiator 4610 and the recipients (sensing responders 4620, 4630, and 4640) may release the resources allocated for the terminated sensing measurement instance.

[0206] Fig.47 An example of an exemplary measurement setup ID information subfield in the sensing measurement setup termination frame action field is illustrated. Fig.47 As shown, the measurement setting ID information subfield may include various information as follows. For example, the subfield may include the number of measurement setting IDs. This may indicate the number of measurement setting information subfields following the measurement setting ID number subfield.

[0207] The information included in the one or more measurement setting information subfields may include one or part of the following information. In some examples, a sensing measurement setting ID and a MAC address of a STA associated with the sensing measurement ID may be included. The STA associated with the sensing measurement ID and / or associated with the indicated MAC address may decode the sensing measurement setting termination frame and terminate the sensing measurement associated with the indicated sensing measurement setting ID.

[0208] In some examples, a sensing measurement ID and / or an STA_ID of an STA associated with the sensing measurement ID may be included. The STA associated with the sensing measurement ID and / or the indicated STA_ID may decode the sensing measurement setup termination frame and terminate the sensing measurement associated with the indicated sensing measurement setup ID. It should be noted that one sensing measurement ID may provide indications for multiple STAs.

[0209] In some examples, a sensing measurement setup ID and / or a STA_ID or MAC address of a sensing initiator associated with the sensing measurement ID may be included. A STA associated with the sensing measurement ID having a corresponding sensing initiator with the indicated STA_ID or MAC address may decode the sensing measurement setup termination frame and terminate the sensing measurement associated with the indicated sensing measurement setup ID.

[0210] In some examples, a sensing measurement setting ID and a sensing group ID may be included. A STA associated with the sensing measurement ID and / or associated with the sensing group ID may decode the sensing measurement setting termination frame and terminate the sensing measurement associated with the indicated sensing measurement setting ID.

[0211] The value in the measurement setting ID number subfield may indicate the number of measurement setting information subfields after the measurement setting ID number. However, it should be noted that other examples of the measurement setting ID information subfield format are also possible. This subfield may include other formats of the elements listed above. In addition, sensing session termination may be used to terminate sensing performed by all STAs involved in the same sensing measurement instance identified by the sensing measurement ID. Sensing session termination may terminate sensing performed by a portion of the STAs involved in the same sensing measurement instance. It should be noted that the above roles may be applied to termination procedures initiated by an AP (not a sensing initiator).

[0212] Embodiments related to termination of sensing measurements initiated by a non-AP STA are described herein. In some cases, termination of a sensing session may be initiated by a non-AP STA.

[0213] Fig.48 An exemplary sensing measurement setup termination procedure initiated by a non-AP STA is illustrated. In the example shown, the sensing responder / termination initiator 4820 (i.e., non-AP STA0) may transmit a message indicating the termination of sensing measurement to the sensing initiator / termination initiator 4810 (i.e., AP), which may indicate the measurement setup ID and / or the non-AP STA involved in the same measurement instance. The sensing initiator / termination initiator 4810 may follow, for example, Fig.45 The same or similar procedures as illustrated and may be used Fig.47The format illustrated is used to notify other non-AP STAs involved in the same measurement setting. Alternatively or additionally, the sensing termination initiator 4820 (e.g., non-AP STA0) may include the group ID in the sensing measurement termination frame. After a period of time (e.g., SIFS) after receiving the measurement termination frame, the sensing initiator / termination responder 4810 may first transmit a sensing measurement termination response frame or ACK to the sensing responder 4820 (i.e., non-AP STA0), and then transmit another sensing measurement termination frame to other responders 4830 and 4840 (i.e., non-AP STAs, i.e., STA1 and STA2). After a period of time (e.g., SIFS) after receiving the sensing measurement termination, the sensing responders 4830 and 4840 (i.e., non-AP STA1 and non-AP STA2) may transmit a sensing measurement termination response and / or ACK to the sensing initiator / termination responder 4810. The resources allocated for the sensing measurement instance may be released.

[0214] Embodiments related to procedures for estimating the number of participating sensing responders per TXOP are described herein.The solution disclosed in this embodiment may be used to solve at least one of the problems defined in the above paragraphs.

[0215] Fig.49 The timing requirements for each stage of the sensing TB measurement instance are illustrated. The time required to complete each stage of the sensing TB measurement instance can be calculated differently for each stage. Fig.49 As shown, the polling phase 4910 may include a polling trigger frame, which is followed by a SIFS, followed by a CTS-to-Self frame. The NDPA detection phase 4920 may include an NDPA, which is followed by a SIFS, followed by an I2R NDP PPDU sent in the downlink. The TF detection phase 4930 may include a detection trigger frame, which is followed by a SIFS, followed by an R2I NDP PPDU sent in the uplink. The reporting phase 4940 may include a report trigger frame, which is followed by a SIFS, followed by a report frame. It is worth noting that the interval between two consecutive phases may be a SIFS.

[0216] In some embodiments, each TB sensing measurement instance may start and complete within a TXOP and should not last beyond the TXOP limit. In some embodiments, there may be one or more polling phases in the same TB measurement instance, and all polling phases may be prioritized in a TB measurement instance. The initiator that initiates a TB measurement instance may end the instance and release the channel if no responder responds with a CTS-to-Self frame.

[0217] In some embodiments, the time T required to complete a polling phase can be calculated according to the following formula:Polling :T Polling =T P-TF +T CTS-to-Self +2×SIFS. T P-TF It can be the time required to send the polling trigger frame, T CTS-to-Self may be the time required to send a CTS to self frame, and SIFS may be the short interframe space.The initiator may estimate the time required to complete a polling phase according to a procedure including one or more of the steps described in the following paragraphs.

[0218] One or more steps may include identifying the number N of responders to be polled for each polling phase. PR One or more steps may include identifying an MCS to be used by the initiator to send the polling trigger frame; identifying a polling trigger frame decoding rate R P-TF ; and / or identifying the polling trigger frame modulation scheme (e.g., the number of bits per modulation sample N P-TF-bps ).

[0219] One or more steps may include identifying an MCS to be used by the polled responder to send a CTS-to-Self frame; identifying a CTS-to-Self frame decoding rate R CTSTS ; and / or identify the polling trigger frame modulation scheme (number of bits per modulation sample N CTSTS-bps );

[0220] One or more steps may include calculating T according to the following formula P-TF :T P-TF =T preamble +N P-TF-SYM ×T P-TF-SYM , where T preamble is the PHY preamble duration including the duration of the signal symbol, N P-TF-SYM is the number of OFDM symbols required to carry the polling trigger frame, and T P-TF-SYM is the symbol interval of the PPDU carrying the polling trigger frame. One or more steps may include calculating the number of OFDM symbols required to carry the polling trigger frame according to the following formula: Where N P-TF-coded-bits can be the number of decoded bits of the polling trigger frame, and N SD is the number of data subcarriers. One or more steps may include calculating the number of decoded bits according to the following formula: Where N P-TF-uncoded-bits It may be the number of undecoded bits of the polling trigger frame. One or more steps may include calculating the number of undecoded bits of the polling trigger frame according to the following formula: P-TF-uncoded-bits =8×(N mac +N common +N user-info N PR+N padding +N FCS ), where N mac Can be the number of octets in the MAC header, N common The number of octets of the common information field of the poll trigger frame, N user-info The number of octets of the User Information field of the Poll Trigger frame, N padding may be the number of octets of the padding field of the Poll Trigger frame, and N FCS Can be the number of octets of the Frame Check Sequence (FCS) field of the Poll Trigger frame.

[0221] One or more steps may include calculating T according to the following formula CTS-to-Self :T CTS-to-Self =T preamble +N CTSTS-SYM ×T CTSTS-SYM , where N CTSTS-SYM can be the number of OFDM symbols required to carry CTS to its own frame, and T CTSTS-SYM It may be the symbol interval of the PPDU carrying the CTS to its own frame. One or more steps may include calculating the number of OFDM symbols required to carry the CTS to its own frame according to the following formula: Where N CTSTS-coded-bits It can be the number of decoded bits from CTS to its own frame, and N SD is the number of data subcarriers. One or more steps may include calculating the number of decoded bits according to the following formula: Where N CTSTS-uncoded-bits It can be the number of undecoded bits from CTS to its own frame. One or more steps may include calculating the number of undecoded bits from CTS to its own frame according to the following formula: CTSTS-uncoded-bits =8×(N CTS ), where N CTS Can be the number of octets of a CTS frame.

[0222] In some embodiments, the time T required to complete an NDPA detection phase can be calculated according to the following formula: NDPA-S :T NDPA-S =T NDPA +T I2R-NDP +2×SIFS. T NDPA can be the time required to send an NDPA frame, and T I2R-NDP It may be the time required to send an I2R NDP PPDU. The initiator may estimate the time required to complete an NDPA probing phase according to a procedure comprising one or more steps as described in the following paragraphs.

[0223] One or more steps may include identifying the number N of responder receivers for each NDPA detection phase. RR .

[0224] One or more steps may include identifying the MCS to be used by the initiator to send the NDPA frame; identifying the NDPA frame decoding rate R NDPA ; and / or identifying the NDPA frame modulation scheme (which may be the number of bits per modulation sample N NDPA-bps ).

[0225] One or more steps may include calculating T according to the following formula NDPA :T NDPA =T preamble +N NDPA-SYM ×T NDPA-SYM , where T preamble The duration of the PHY preamble, N, which may be the duration of the signal symbol, NDPA-SYM may be the number of OFDM symbols required to carry the NDPA frame, and T NDP-SYM It may be the symbol interval of the PPDU carrying the NDPA frame. One or more steps may include calculating the number of OFDM symbols required to carry the NDPA frame according to the following formula: Where N NDPA-coded-bits can be the number of decoded bits of the NDPA frame, and N SD It can be the number of data subcarriers. One or more steps may include calculating the number of decoded bits according to the following formula: Where N NDPA-uncoded-bits It may be the number of undecoded bits of the NDPA frame. One or more steps may include calculating the number of undecoded bits of the NDPA frame according to the following formula: NDPA-uncoded-bits =8×(N mac +N SDT +N sta-info N RR ++N FCS ), where N mac can be the number of octets in the MAC header, N SDT The number of octets that may be in the Probe Dialog Token field of the NDPA frame, N sta-info may be the number of octets of the STA Information field of the NDPA frame, and N FCS May be the number of octets of the Frame Check Sequence (FCS) field of the NDPA frame.

[0226] One or more steps may include calculating T according to the following formula I2R-NDP : Where T NDP-PreambleIt can be the sending time of the preamble of I2R NDP PPDU, N LTF-REP (n) may be the number of LTF repetitions per responder receiver, N NDP-LTF (n) may be the number of LTFs per responder receiver of the I2R NDP PPDU, T NDP-LTF-SYM It can be the LTF symbol time of I2R NDP PPDU, T PE It can be a packet extension time, and SignalExtension can be a signal extension that can depend on the spectrum.

[0227] In some embodiments, the time T required to complete a TF detection phase can be calculated according to the following formula: TF-S :T TF-S =T S-TF +T R2I-NDP +2×SIFS. T S-TF can be the time required to send a detection trigger frame, and T R2I-NDP It may be the time required to send the R2I NDP PPDU. The initiator may estimate the time required to complete a TF probing phase according to a procedure comprising one or more steps as described in the following paragraphs.

[0228] One or more steps may include identifying the number N of responder transmitters per TF detection phase RT .

[0229] One or more steps may include identifying an MCS to be used by the initiator to send the probe trigger frame; identifying a probe trigger frame decoding rate R S-TF ; and / or identify the detection trigger frame modulation scheme (number of bits per modulation sample N S-TF-bps ).

[0230] One or more steps may include calculating T according to the following formula S-TF :T S-TF =T preambl e+N S-TF-SYM ×T S-TF-SYM , where T preamble The duration of the PHY preamble, N, which may be the duration of the signal symbol, S-TF-SYM can be the number of OFDM symbols required to carry the detection trigger frame, and T S-TF-SYM It may be the symbol interval of the PPDU carrying the detection trigger frame. One or more steps may include calculating the number of OFDM symbols required to carry the detection trigger frame according to the following formula: Where N S-TF-coded-bits can be the number of decoded bits of the polling trigger frame, and N SDIt can be the number of data subcarriers. One or more steps may include calculating the number of decoded bits according to the following formula: Where N S-TF-uncoded-bits It may be the number of undecoded bits of the detection trigger frame. One or more steps may include calculating the number of undecoded bits of the detection trigger frame according to the following formula: S-TF-uncoded-bits =8×(N mac +N common +N user-info N RT +N padding +N FCS ), where N mac Can be the number of octets in the MAC header, N common The number of octets that may be the common information field of the detection trigger frame, N user-info The number of octets of the User Information field of the Probe Trigger Frame, N padding may be the number of octets of the padding field of the Probe Trigger Frame, and N FCS May be the number of octets of the Frame Check Sequence (FCS) field of the Probe Trigger Frame.

[0231] One or more steps may include calculating T according to the following formula R2I-NDP : Where T NDP-Preamble is the sending time of the preamble of I2R NDP PPDU, N LTF-REP (n) is the number of LTF repetitions per responder transmitter, N NDP-LTF (n) is the number of LTFs per responder transmitter of the R2INDP PPDU, T NDP-LTF-SYM is the LTF symbol time of the R2I NDPPPDU, T PE is the packet extension time, and SignalExtension is the signal extension depending on the spectrum.

[0232] In some embodiments, the time required to complete a reporting phase can be calculated according to the following formula: TF-R :T TF-R =T R-TF +T Report +2×SIFS, where T S-TF can be the time required to send a report trigger frame, and T Report It may be the time required to send a report frame. The initiator may estimate the time required to complete a reporting phase according to a procedure comprising one or more steps as described in the following paragraphs.

[0233] One or more steps may include identifying the number N of responders that are triggered to transmit their measurement feedback reports in each reporting phase. RF .

[0234] One or more steps may include identifying an MCS to be used by the initiator to send a report trigger frame; identifying a report trigger frame decoding rate R R-TF ; and / or identify the report trigger frame modulation scheme (number of bits per modulation sample N R-TF-bps ).

[0235] One or more steps may include identifying an MCS to be used by the responder to send the report frame; identifying a report frame decoding rate R FR ; and / or identify the reporting frame modulation scheme (number of bits per modulation sample N FR-bps ).

[0236] One or more steps may include calculating T according to the following formula R-TF :T R-TF =T preamble +N R-TF-SYM ×T R-TF-SYM , where T preamble The duration of the PHY preamble, N, which may be the duration of the signal symbol, R-TF-SYM may be the number of OFDM symbols required to carry the report trigger frame, and T R-TF-SYM It may be the symbol interval of the PPDU carrying the report trigger frame. One or more steps may include calculating the number of OFDM symbols required to carry the report trigger frame according to the following formula: Where N R-TF-coded-bits can be the number of decoded bits of the report trigger frame, and N SD It can be the number of data subcarriers. One or more steps may include calculating the number of decoded bits according to the following formula: Where N R-TF-uncoded-bits It may be the number of undecoded bits of the report trigger frame. One or more steps may include calculating the number of undecoded bits of the report trigger frame according to the following formula: R-TF-uncoded-bits =8×(N mac +N common +N user-info N RF +N padding +N FCS ), where N mac Can be the number of octets in the MAC header, N common It can be the number of octets of the common information field of the report trigger frame, N user-info It can be the number of octets of the User Information field of the Report Trigger frame, N paddingmay be the number of octets of the padding field of the Report Trigger Frame, and N FCS It can be the number of octets of the Frame Check Sequence (FCS) field of the reporting trigger frame.

[0237] One or more steps may include calculating T according to the following formula Report :T Report =T preamble +N Report-SYM ×T Report-SYM , where T preamble It can be the TB-PPDU PHY preamble duration, N Report-SYM may be the number of OFDM symbols required to carry the report frame, and T Report-SYM is the symbol interval of the TB-PPDU carrying the report frame. One or more steps may include calculating the number of OFDM symbols required to carry the report frame according to the following formula: Where N Report-coded-bits can be the number of decoded bits of the reporting frame, and N SD It can be the number of data subcarriers. One or more steps may include calculating the number of decoded bits according to the following formula: Where N Report-uncoded-bits It may be the number of undecoded bits of the report frame. One or more steps may include calculating the number of undecoded bits of the report frame according to the following formula: Where N mac can be the number of octets in the MAC header, N report-control The number of octets that may be in the Report Control field of a report frame, N reports It can be the number of aggregate reports in the reporting frame, N ReportField (r) may be the number of octets reporting r, N padding may be the number of octets of the padding field of the report frame, and N FCS May be the number of octets of the Frame Check Sequence (FCS) field of the reporting frame.

[0238] In some embodiments, given the duration of a corresponding sensing TXOP and the total number of responders N polled responders In this case, the initiator may estimate the maximum number of responder transmitters that may participate in the TF probing phase of a TB sensing measurement instance according to a procedure comprising one or more steps as described in the following paragraphs.

[0239] One or more steps may include identifying which phases will be in the TB sensing measurement instance under consideration; calculating the time T required for one polling phase; polling ; and / or calculate the number of polling phases N required to poll all responders according to the following formularesponders :

[0240] One or more steps may include calculating the time T required to perform the NDPA detection phase NDPA-total =N NDPA ×T NDPA-S , where N NDPA It may be the number of NDPA phases in a TB sensing measurement instance. This parameter may be implementation specific.

[0241] One or more steps may include calculating the time T required to perform the reporting phase Reporting-total =N Reporting ×T Reporting , where N Reporting It may be the number of reporting phases in a TB sensing measurement instance. This parameter may be implementation specific.

[0242] Based on the phase considered in the TB sensing measurement example, the maximum number of responder transmitters that can participate in the TF detection phase can be calculated as Where TXOP can be the TXOP duration, T phase (m) may be the time required to perform phase m, and M may be the total number of all phases considered in the TB sensing measurement instance.

[0243] Although the features and elements of the present invention are described in a specific combination in a preferred embodiment, each feature or element may be used alone without other features and elements of the preferred embodiment, or in various combinations with or without other features and elements of the present invention. Although the solution described herein considers 802.11 specific protocols, it should be understood that the solution described herein is not limited to this scenario and is also applicable to other wireless systems. Although the term SIFS may be used to indicate various inter-frame intervals in examples of designs and procedures, other inter-frame intervals such as RIFS, AIFS, DIFS or other agreed time intervals may be used interchangeably in the same solution. Although four RBs per triggered TXOP may be shown as an example in some figures, the number of RBs / channels / bandwidths actually utilized may vary. For example, although a specific bit may be used to signal the in-BSS / OBSS state, other bits may be used to signal the information. Although some trigger type values ​​or items may be used as examples to identify newly defined trigger frame variants, other values ​​or items may be used. The terms multi-AP and MAP are used interchangeably to refer to the same concept. The Long Training Field (LTF) may be any type of predefined sequence known at both the transmitter and receiver sides.

[0244] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (sent via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method performed by a sensing responder, the method comprising: receiving a first sensing measurement setup request message from a sensing initiator, the first sensing measurement setup request message indicating first one or more parameters to be used by the sensing responder in a sensing measurement procedure; sending a first sensing measurement setup response message to the sensing initiator, the first sensing measurement setup response message indicating at least one parameter different from the first one or more parameters indicated by the sensing measurement setup request message; receiving, from the sensing initiator, a second sensing measurement setup request message based on the indicated at least one parameter different from the first one or more parameters, the second sensing measurement setup request message indicating second one or more parameters to be used by the sensing responder in the sensing measurement procedure, wherein the second one or more parameters to be used by the sensing responder in the sensing measurement procedure include at least one parameter different from the first one or more parameters indicated by the first sensing measurement setup request message; sending a second sensing measurement setup response message to the sensing initiator, wherein the second sensing measurement setup response message indicates a successful sensing measurement setup procedure; as well as The sensing measurement procedure is participated in using the second one or more parameters. 2 . The method of claim 1 , wherein the first sensing measurement setup response message indicates a rejection of at least one of the first one or more parameters indicated by the first sensing measurement setup request message. 3 . The method of claim 1 , wherein the at least one parameter indicated by the first sensing measurement setup response message comprises an alternative parameter to at least one of the first one or more parameters indicated by the first sensing measurement setup request message.

4. The method of claim 1 , wherein the second sensing measurement setup response indicating the successful sensing measurement setup procedure is sent based on the second sensing measurement setup request message, the second sensing measurement setup request message including a parameter consisting of the at least one parameter indicated by the first sensing measurement setup response message. 5 . The method of claim 1 , further comprising measuring a channel condition between the sensing responder and at least one other participant in the sensing measurement procedure.

6. The method of claim 1, further comprising transmitting or receiving a transmission indicating resources for sending a report including an indication of a measured channel condition between the sensing responder and the at least one other participant in the sensing measurement procedure.

7. The method of claim 6, wherein the transmitted or received transmission indicating resources for sending the report is a trigger frame.

8. The method of claim 1, further comprising sending or receiving a Null Data Packet (NDP) frame to be measured during the sensing measurement procedure.

9. The method of claim 1, wherein the sensing initiator is an access point (AP)-station (STA), and the sensing responder is a non-AP-STA.

10. The method of claim 1, wherein the sensing initiator is a non-AP-STA, and the sensing responder is an AP-STA.

11. A sensing responder, comprising: processor; and Transceiver; The processor and the transceiver are configured to receive a first sensing measurement setup request message from a sensing initiator, the first sensing measurement setup request message indicating first one or more parameters to be used by the sensing responder in a sensing measurement procedure; The processor and the transceiver are configured to send a first sensing measurement setup response message to the sensing initiator, the first sensing measurement setup response message indicating at least one parameter different from the first one or more parameters indicated by the first sensing measurement setup request message; the processor and the transceiver being configured to receive, from the sensing initiator, a second sensing measurement setup request message based on the indicated at least one parameter different from the first one or more parameters, the second sensing measurement setup request message indicating second one or more parameters to be used by the sensing responder in the sensing measurement procedure, wherein the second one or more parameters to be used by the sensing responder in the sensing measurement procedure include at least one parameter different from the first one or more parameters indicated by the first sensing measurement setup request message; The processor and the transceiver are configured to send a second sensing measurement setup response message to the sensing initiator, the second sensing measurement setup response message indicating a successful sensing measurement setup procedure; and The processor and the transceiver are configured to transmit or receive a transmission using the second one or more parameters to participate in the sensing measurement procedure. 12 . The sensing responder of claim 11 , wherein the first sensing measurement setup response message indicates a rejection of at least one of the first one or more parameters indicated by the first sensing measurement setup request message. 13 . The sensing responder of claim 11 , wherein the at least one parameter indicated by the first sensing measurement setup response message comprises an alternative parameter to at least one of the first one or more parameters indicated by the first sensing measurement setup request message.

14. The sensing responder of claim 11, wherein the second sensing measurement setup response indicating the successful sensing measurement setup procedure is sent based on the second sensing measurement setup request message, the second sensing measurement setup request message including parameters consisting of the at least one parameter indicated by the first sensing measurement setup response message.

15. The sensing responder of claim 11, the processor and the transceiver further configured to measure a channel condition between the sensing responder and at least one other participant in the sensing measurement procedure.

16. The sensing responder of claim 11, the processor and the transceiver being further configured to transmit or receive a transmission indicating resources for sending a report, the report comprising an indication of a measured channel condition between the sensing responder and the at least one other participant in the sensing measurement procedure.

17. The sensing responder of claim 16, wherein the transmitted or received transmission indicating resources for sending the report is a trigger frame.

18. The sensing responder of claim 11, the processor and transceiver further configured to transmit or receive a Null Data Packet (NDP) frame to be measured during the sensing measurement procedure.

19. The sensing responder of claim 11, wherein the sensing initiator is an access point (AP)-station (STA), and the sensing responder is a non-AP-STA.

20. The sensing responder of claim 11, wherein the sensing initiator is a non-AP-STA, and the sensing responder is an AP-STA.

Images