COMMUNICATION APPARATUS AND METHOD FOR EXPANDED SENSING BY PROXY - Patent application

Abstract

The present disclosure provides a communications device and a communications method for proxy sensing, the communications device comprising: a circuit configured, in operation, to generate a request frame indicating conditions to be used by a second communications device to select one or more links, each of which is coupled to one or more third communications devices; a transmitter, in operation, to transmit the request frame to the second communications device to request the second communications device to perform measurements on the one or more links; and a receiver, in operation, to receive a report frame from the second communications device, the report frame including one or more reports of the measurements corresponding to the one or more links.

Description

[Technical field]

[0001] TECHNICAL FIELD The present disclosure relates to a communication apparatus and method for sensing, and more particularly for sensing by a proxy. [Background technology]

[0002] Wireless local area network (WLAN) sensing is being developed by the Institute of Electrical and Electronics Engineers (IEEE) 802.11bf Task Group. The task group has proposed Sensing by Proxy (SBP) that allows a client to obtain sensing measurements by using multiple wireless links, but the details of the protocol / procedure for selecting the best link / STA in the SBP procedure have not been discussed in the task group.

[0003] Wi-Fi coverage with multiple links is very common today, but blindly measuring and reporting all possible links in the SBP reporting phase would cause a large overhead in the Wi-Fi links used for reporting.

[0004] Therefore, there is a need for a communication apparatus and method for enhanced sensing by a proxy that provides a viable technical solution to address the problem, and more specifically, that enables an SBP initiator and / or an SBP responder to select the best link / STA to reduce reporting overhead in an SBP procedure.

[0005] Furthermore, other desirable features and characteristics will become apparent from the following detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background of disclosure. Summary of the Invention [Problem to be solved by the invention]

[0006] Non-limiting and exemplary embodiments facilitate providing a communications apparatus and method for a collaborative sounding procedure in the context of a WLAN. [Means for solving the problem]

[0007] In a first aspect, the present disclosure provides a first communications device comprising: circuitry configured, in operation, to generate a request frame indicating conditions to be used by a second communications device to select one or more links, each linked to one or more third communications devices; a transmitter, in operation, to transmit the request frame to the second communications device to request the second communications device to perform measurements on the one or more links; and a receiver, in operation, to receive from the second communications device a report frame including one or more reports of the measurements corresponding to the one or more links.

[0008] In a second aspect, the present disclosure provides a second communications device comprising: a receiver configured, in operation, to receive a request frame from a first communications device indicating conditions for selecting one or more links, each of which is coupled to one or more third communications devices; circuitry configured, in operation, to generate a report frame including one or more reports of measurements corresponding to the one or more links; and a transmitter configured, in operation, to transmit the report frame to the first communications device.

[0009] In a third aspect, the present disclosure provides a communication method implemented by a first communication device, comprising: generating a request frame indicating conditions to be used by a second communication device to select one or more links, each of which is coupled to one or more third communication devices; transmitting the request frame to the second communication device to request the second communication device to perform measurements on the one or more links; and receiving a report frame from the second communication device, the report frame including one or more reports of the measurements corresponding to the one or more links.

[0010] In a fourth aspect, the present disclosure provides a communication method implemented by a second communication device, comprising: receiving a request frame from a first communication device indicating conditions for selecting one or more links, each of which is coupled to one or more third communication devices; generating a report frame including one or more reports of measurements corresponding to the one or more links; and transmitting the report frame to the first communication device.

[0011] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any combination thereof.

[0012] Further advantages and benefits of an embodiment of the present disclosure will become apparent from the specification and drawings, in which such advantages and / or benefits are provided by some of the embodiments and features described in the specification and drawings, respectively, but not necessarily all of which are provided to obtain one or more identical features.

[0013] Embodiments of the present disclosure, by way of example only, will be better understood and readily apparent to those skilled in the art from the following description and in conjunction with the drawings, in which: [Brief description of the drawings]

[0014] [Figure 1]A schematic diagram showing single-user (SU) communication between an access point (AP) and a station (STA) in a multiple-input multiple-output (MIMO) wireless network. [Diagram 2] Schematic diagram showing downlink multi-user (MU) communication between an AP and multiple STAs in a MIMO wireless network. [Diagram 3] A schematic diagram showing trigger-based (TB) uplink MU communication between an AP and multiple STAs in a MIMO wireless network. [Figure 4] Schematic diagram showing communication between STA (Client 0) and AP for Basic SBP procedure [Diagram 5] Floor plan and schematic showing devices located on the floor [Figure 6] Schematic diagram of a communication device according to the present disclosure. [Figure 7] 1 is a flowchart illustrating a communication method implemented by a first communication device according to various embodiments of the present disclosure. [Figure 8] 1 is a flowchart illustrating a communication method implemented by a second communication device according to various embodiments of the present disclosure. [Figure 9] 1 is a flowchart outlining a procedure for proxy sensing between an AP and three non-AP STAs according to a first embodiment of the present disclosure; [Figure 10] FIG. 10 is a flowchart showing a detailed procedure flow of the proxy sensing procedure between the AP and three non-AP STAs in FIG. [Figure 11] A schematic diagram showing the connections between the AP and three non-AP STAs in FIG. [Figure 12] An exemplary format of an extended capabilities element used for basic discovery according to one embodiment of the present disclosure [Figure 13A] An exemplary format of an SBP Request frame according to the first embodiment of the present disclosure [Figure 13B] An exemplary format of a Protected SBP Request frame according to a first embodiment of the present disclosure [Figure 14A] An exemplary format of an SBP Response frame according to the first embodiment of the present disclosure [Figure 14B] An exemplary format of a Protected SBP Response frame according to a first embodiment of the present disclosure [Figure 15] Exemplary Format of the SBP Parameters Element Field in the SBP Request / Response Frames of FIGS. 13A-14B [Figure 16] Exemplary Format of the SBP Link Information Element Field in the SBP Response Frame of FIGS. 14A and 14B [Figure 17] An exemplary format of an SBP Report frame according to the first embodiment of the present disclosure [Figure 18A] Exemplary format of an SBP Termination frame according to the first embodiment of the present disclosure [Figure 18B] An exemplary format of a Protected SBP Termination frame according to the first embodiment of the present disclosure. [Figure 19] FIG. 1 is a flowchart illustrating communication between an SBP initiator (non-AP STA) and an SBP responder (AP) for sensing by a proxy according to a first embodiment of the present disclosure. [Figure 20A] 1 is a flowchart outlining a procedure for proxy sensing between an AP and three non-AP STAs according to a second embodiment of the present disclosure; [Figure 20B] A schematic diagram showing the connection between the AP and three non-AP STAs in FIG. 20A. [Figure 21] FIG. 20B is a flowchart showing a detailed procedure flow of the proxy sensing procedure between the AP and three non-AP STAs in FIG. 20A. [Figure 22] FIG. 1 shows an example visualization of enhanced client discovery results. [Diagram 23] An exemplary format of an SBP parameter element field of an SBP request frame according to a second embodiment of the present disclosure. [Figure 24A] An exemplary format of an SBP response according to the second embodiment of the present disclosure [Figure 24B] An exemplary format of a protected SBP response according to the second embodiment of the present disclosure [Diagram 25] Exemplary Format of the SBP Link Information Element Field in the SBP Response Frame of FIG. 24A and FIG. 24B According to an Embodiment [Figure 26] Exemplary format of an SBP report frame according to a second embodiment of the present disclosure [Figure 27A] FIG. 2 is a schematic diagram showing a floor plan and devices located on the floor together with two exemplary implementations of a proxy sensing procedure according to a second embodiment of the present disclosure; [Figure 27B] Another exemplary format of the SBP request frame according to the second embodiment of the present disclosure [Figure 28] 11 is a flowchart outlining a procedure for proxy-based sensing between an AP and three non-AP STAs according to a third embodiment of the present disclosure. [Figure 29] 11 is a flowchart illustrating an embodiment of a procedure for proxy sensing between an AP and two non-AP STAs according to a third embodiment of the present disclosure; [Diagram 30] An exemplary format of a sensing measurement setup request frame according to a third embodiment of the present disclosure. [Diagram 31] An exemplary format of a Protected Authorization Validation Request frame according to a third embodiment of the present disclosure. [Diagram 32]An exemplary format of a Protected Authorization Validation Response frame according to a third embodiment of the present disclosure. [Figure 33A] Exemplary format of an SBP response frame according to a third embodiment of the present disclosure [Figure 33B] Exemplary Format of a Protected SBP Response Frame According to a Third Embodiment of the Present Disclosure [Diagram 34] Exemplary format of an SBP request frame according to a third embodiment of the present disclosure [Diagram 35] FIG. 1 illustrates an exemplary configuration of a communication device. [Diagram 36] FIG. 1 illustrates another exemplary configuration of a communication device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Those skilled in the art will appreciate that the elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale For example, the dimensions of some of the elements in the figures, block diagrams or flow charts may be exaggerated relative to other elements to facilitate an accurate understanding of the present embodiments.

[0016] Some embodiments of the present disclosure are now described, by way of example, with reference to the drawings in which like reference numbers and letters indicate similar or equivalent elements.

[0017] In the following paragraphs, exemplary embodiments are described with particular reference to access points (APs) and stations (STAs) for sensing by proxy in a multiple-input multiple-output (MIMO) wireless network.

[0018] In the context of IEEE 802.11 (Wi-Fi) technology, a station (also referred to as STA) is a communication device capable of using the 802.11 protocol. Based on the definition of IEEE 802.11-2016, a STA can be any device that includes an IEEE 802.11 compliant Media Access Control (MAC) and physical layer (PHY) interface to a Wireless Medium (WM).

[0019] For example, a STA may be a laptop, a desktop personal computer (PC), a personal digital assistant (PDA), an access point, or a Wi-Fi phone in a wireless local area network (WLAN) environment. A STA may be stationary or mobile. In a WLAN environment, the terms "STA," "wireless client," "user," "user device," and "node" are often used interchangeably.

[0020] Similarly, an AP, which may be interchangeably referred to as a Wireless Access Point (WAP) in the context of IEEE 802.11 (Wi-Fi) technology, is a communications device that enables STAs in a WLAN to connect to a wired network. APs typically connect to a router (through a wired network) as standalone devices, but may also be integrated with or used within a router.

[0021] As mentioned above, a STA in a WLAN may operate as an AP in other cases, and vice versa. This is because a communication device in the context of IEEE 802.11 (Wi-Fi) technology may include both STA and AP hardware components. In this manner, the communication device may switch between STA and AP modes based on the conditions and / or requirements of the actual WLAN.

[0022] In a MIMO wireless network, "multiple" refers to multiple antennas used simultaneously for transmission and multiple antennas used simultaneously for reception over a wireless channel. In this regard, "multiple-input" refers to multiple transmitter antennas that input wireless signals to a channel, and "multiple-output" refers to multiple receiver antennas that receive wireless signals from the channel to a receiver. For example, in an N×M MIMO network system, N is the number of transmitter antennas and M is the number of receiver antennas, and N may or may not be equal to M. For simplicity, the respective numbers of transmitter antennas and receiver antennas will not be further described in this disclosure.

[0023] In a MIMO wireless network, single-user (SU) and multi-user (MU) communications can be deployed for communication between communication devices such as APs and STAs. MIMO wireless networks have advantages such as spatial multiplexing and spatial diversity, which enable higher data rates and robustness through the use of multiple spatial streams. According to various embodiments, the term "spatial stream" may be used interchangeably with the term "space-time stream" (or STS).

[0024] FIG. 1 shows a schematic diagram of SU communication 100 between an AP 102 and a STA 104 in a MIMO wireless network. As shown, the MIMO wireless network may include one or more STAs (e.g., STA 104, STA 106, etc.). If the SU communication 100 in the channel is performed over the entire channel bandwidth, it is called full bandwidth SU communication. If the SU communication 100 in the channel is performed over a portion of the channel bandwidth (e.g., one or more 20 MHz subchannels in the channel are punctured), it is called punctured SU communication. In the SU communication 100, the AP 102 transmits multiple space-time streams using multiple antennas (e.g., four antennas as shown in FIG. 1) with all space-time streams directed to a single communication device, i.e., the STA 104. For simplicity, the multiple space-time streams directed to the STA 104 are shown as arrows 108 of grouped data transmissions directed to the STA 104.

[0025] SU communication 100 can be configured for bidirectional transmission. As shown in FIG. 1A, in SU communication 100, STA 104 may transmit multiple space-time streams using multiple antennas (e.g., two antennas as shown in FIG. 1) with all space-time streams directed to AP 102. For simplicity, the multiple space-time streams directed to AP 102 are shown as grouped data transmission arrows 110 directed to AP 102.

[0026] Thus, the SU communication 100 shown in FIG. 1 allows for both uplink and downlink SU transmissions in a MIMO wireless network.

[0027] FIG. 2 is a schematic diagram illustrating downlink multiple-user (MU) communication 200 between an AP 202 and multiple STAs 204, 206, 208 in a MIMO wireless network. The MIMO wireless network may include one or multiple STAs (e.g., STA 204, STA 206, STA 208, etc.). The MU communication 200 can be an Orthogonal Frequency Division Multiple Access (OFDMA) communication or a MU-MIMO communication. For OFDMA communication in a channel, the AP 202 transmits multiple streams simultaneously to the STAs 204, 206, 208 in the network on different resource units (RUs) in the channel bandwidth. For MU-MIMO communication in a channel, the AP 202 transmits multiple streams simultaneously to the STAs 204, 206, 208 on the same one or more RUs in the channel bandwidth using multiple antennas via spatial mapping or precoding techniques. When the RUs in which OFDMA or MU-MIMO communication take place occupy the entire channel bandwidth, the OFDMA or MU-MIMO communication is referred to as full-bandwidth OFDMA or full-bandwidth MU-MIMO communication. When the RUs in which OFDMA or MU-MIMO communication take place occupy a portion of the channel bandwidth (e.g., when one or more 20 MHz subchannels in the channel are punctured), the OFDMA or MU-MIMO communication is referred to as punctured OFDMA or punctured MU-MIMO communication. For example, two space-time streams may be directed to the STA 206, one other space-time stream may be directed to the STA 204, and one other space-time stream may be directed to the STA 208. For simplicity, the two space-time streams directed to the STA 206 are shown as grouped data transmission arrow 212, the space-time stream directed to the STA 204 is shown as data transmission arrow 210, and the space-time stream directed to the STA 208 is shown as data transmission arrow 214.

[0028] To enable uplink MU transmissions, trigger-based communication is provided in a MIMO wireless network. In this regard, Figure 3 shows a schematic diagram of trigger-based (TB) uplink MU communication 300 between an AP 302 and multiple STAs 304, 306, 308 in a MIMO wireless network.

[0029] Because there are multiple STAs 304, 306, 308 participating in trigger-based uplink MU communications, the AP 302 needs to coordinate the simultaneous transmissions of the multiple STAs 304, 306, 308.

[0030] For coordination, as shown in FIG. 3, the AP 302 may simultaneously transmit trigger frames 310, 314, 318 to the STAs 304, 306, 308 to indicate user-specific resource allocation information (e.g., number of space-time streams, starting STS number, and assigned RU) that each STA may use. The STAs 304, 306, 308 may then simultaneously transmit their respective space-time streams to the AP 302 in response to the trigger frames according to the user-specific resource allocation information indicated in the trigger frames 310, 314, 318. For example, two space-time streams may be directed from the STA 306 to the AP 302, one other space-time stream may be directed from the STA 304 to the AP 302, and one other space-time stream may be directed from the STA 308 to the AP 302. For simplicity, the two space-time streams directed from STA 306 to AP 302 are shown as grouped data transmission arrow 316, the space-time stream directed from STA 304 to AP 302 is shown as data transmission arrow 312, and the space-time stream directed from STA 308 to AP 302 is shown as data transmission arrow 320.

[0031] Due to the packet / PPDU (Physical Layer Protocol Data Unit) based transmission and distributed MAC (Medium Access Control) scheme in 802.11 WLAN, there is no time scheduling (e.g., TDMA (Time Division Multiple Access)-like periodic time slot allocation for data transmission) in 802.11 WLAN. Frequency and space resource scheduling is performed on a packet basis; that is, the resource allocation information is in units of PPDU.

[0032] According to various embodiments, the WLAN supports non-triggered based communication as shown in Figure 1 and triggered based communication as shown in Figure 2. In non-triggered based communication, a communication device transmits PPDUs to one other communication device or one or more other communication devices in an unsolicited manner. In triggered based communication, a communication device transmits PPDUs to one other communication device or one or more other communication devices only upon receiving a request for a trigger frame.

[0033] In this disclosure, the term "sensing initiator" refers to a device that initiates a sensing session with a STA (hereinafter also referred to as a "client") and requests a sensing result from the STA. The term "sensing responder" refers to a STA that responds to the sensing initiator and participates in the sensing session. In the following various embodiments, unless otherwise specified, the initiator and the responder refer to "sensing initiator" and "sensing responder", respectively. Typically (e.g., in trigger-based (TB) sensing measurements), the initiator is an AP and the responder is a non-AP STA. However, this need not always be the case, and sometimes (e.g., in non-TB sensing measurements, or Fine Timing Measurements (FTM) / ranging), a non-AP STA may be the initiator and an AP may be the responder.

[0034] In contrast to "sensing initiator" and "sensing responder," the term "sensing by proxy (SBP) initiator" refers to a STA that initiates an SBP procedure and requests a device (e.g., an AP or sensing initiator) to be a proxy sensing initiator to initiate a sensing session and request sensing results from another STA (e.g., a client of the device) on behalf of the SBP initiator. An "SBP responder" refers to a device that responds to the SBP initiator and agrees to be a proxy sensing initiator and participates in the SBP procedure. It should be noted that an SBP initiator can be a sensing responder or one of multiple sensing responders of an SBP responder (sensing initiator).

[0035] As mentioned above, SBP, which allows a client to obtain sensing measurements using multiple wireless links, is introduced in IEEE 802.11bf. FIG. 4 is a schematic diagram 400 illustrating communication between a STA (client 0) and an AP for a basic SBP procedure. According to the basic concept, the procedure of sensing by proxy includes SBP procedure setup, sensing measurement, SBP procedure report, and SBP procedure termination. During the SBP procedure setup, a client (e.g., client 0) requests the AP to obtain sensing measurements with other clients (e.g., clients 1 and 2). The AP is configured to act as a proxy initiator for the requesting client. In various embodiments shown in this disclosure, such a requesting client is called an SBP requesting STA or an SBP initiator, while the AP is called a proxy AP or an SBP responder. The proxy is established by exchanging SBP request / response frames 412 between the SBP initiator and the SBP responder. The AP then performs sensing measurements with one or more clients (e.g., clients 1 and 2) by, for example, exchanging measurement setup request / response frames to establish a session and / or measurement report frames 414a, 414b during a measurement instance. In the example of FIG. 4, the SBP initiator is one of the clients, but the AP may also perform sensing measurements with the SBP initiator by exchanging associated frames 414c. During the SBP procedure reporting, the AP that has obtained the measurement reports of the clients then reports them to the SBP initiator, for example, by sending an SBP report frame 416. After the SBP procedure reporting, the SBP procedure may be terminated at any time by either the SBP initiator or the SBP responder sending an SBP end frame (not shown).

[0036] As mentioned before, there is a problem with client discovery in the SBP procedure. Since the coverage of the whole house / office / building / entity by multi-AP Wi-Fi (e.g., by mesh Wi-Fi or enterprise Wi-Fi network) is very common nowadays, blindly measuring and reporting all possible links in the SBP reporting phase will cause a large overhead in the Wi-Fi links used for reporting. Figure 5 shows a schematic diagram 500 showing a floor plan and devices arranged on the floor. In this figure, STA-8 is an SBP initiator 502 configured to perform people tracking for people entering through door 504. As shown using lines between devices, there may be 15 possible links between devices, but only a few links such as links 506, 507, 508, 509, and 510 (among STA-5, phone-1, AP-1) may be interesting links for the application of people tracking sensing responsible for people tracking near door 504.

[0037] Therefore, there is a need for a communication apparatus and method for enhanced sensing by a proxy that enables an SBP initiator to select the best link / STA in an SBP procedure to reduce reporting overhead.

[0038] This disclosure presents a proxy-based sensing procedure that allows a non-AP STA to become an SBP initiator during the SBP negotiation phase and select a STA or link for sensing measurement. The link may be an AP-to-STA link (e.g., an initiator-to-responder link (I2R) or a responder-to-initiator link (R2I)), or a STA-to-STA link (e.g., a responder-to-responder link (R2R)). This disclosure also aims to propose related signaling and frame formats for the proxy-based sensing procedure.

[0039] 6 illustrates a schematic diagram of a communication device 600 according to the present disclosure. The communication device 600 may also be implemented as a sensing initiator, a sensing responder, an SBP initiator, or an SBP responder.

[0040] As shown in Figure 6, the communication device 600 may include a circuit 614, at least one wireless transmitter 802, at least one wireless receiver 604, and at least one antenna 612 (for simplicity, only one antenna is shown in Figure 6 for illustrative purposes). The circuit 614 may include at least one controller 606 for use in software and hardware assisted execution of the tasks that the at least one controller 606 is designed to perform, including control of communications with one or more other communication devices in a MIMO wireless network. The circuit 614 may further include at least one transmit signal generator 608 and at least one receive signal processor 610. At least one controller 606 may control at least one transmit signal generator 608 to generate MAC frames and PPDUs to be transmitted to one or more other communication devices via at least one wireless transmitter 602, where the MAC frames may be, for example, a Client Discovery Query / Request / Response frame, a Sensing Measurement Setup Request / Response frame, an SBP Request / Response frame, an SBP Report frame, a Sensing Measurement Report frame, a Polling Trigger frame, a Sounding Trigger frame, an NFRP Trigger frame, a Sensing Trigger frame, a Sensing NDPA (Non-Provisional Address Resolution Protocol) frame, a ... The PPDU may be, for example, a PPDU used for non-trigger-based communication, a PPDU used for a trigger-based sounding / sensing measurement procedure, a PPDU used for a non-trigger-based sounding / sensing measurement procedure, a PPDU used for trigger-based downlink transmission when the communication device 600 is an AP, or a PPDU used for trigger-based uplink transmission when the communication device 600 is a STA.At least one control unit 606 may control at least one receiving signal processing unit 610 to process MAC frames and PPDUs received from one or more other communication devices via at least one wireless receiving unit 604 under the control of the at least one control unit 606, where the MAC frames may be, for example, client discovery query / request / response frames, sensing measurement setup request / response frames, SBP request / response frames, SBP report frames, sensing measurement report frames, polling trigger frames, sounding trigger frames, NFRP trigger frames, sensing trigger frames, sensing NDPA, and the PPDUs may be, for example, PPDUs used for non-triggered communication, PPDUs used for triggered sounding / sensing measurement procedures, non-triggered sounding / sensing measurement procedure PPDUs used for triggered uplink transmissions when the communication device 600 is an AP, or PPDUs used for triggered downlink transmissions when the communication device 600 is a STA. At least one transmission signal generating unit 608 and at least one reception signal processing unit 610 may be standalone modules of the communication device 600 that communicate with at least one control unit 606 for the above-mentioned functions as shown in FIG. 6. Alternatively, at least one transmission signal generating unit 608 and at least one reception signal processing unit 610 may be included in at least one control unit 606. It is obvious to those skilled in the art that the arrangement of these functional modules is flexible and may vary according to actual needs and / or requirements. Data processing, storage, and other related control devices may be provided on a suitable circuit board and / or in a chipset. In various embodiments, in operation, at least one wireless transmitting unit 802, at least one wireless receiving unit 604, and at least one antenna 612 may be controlled by at least one control unit 606.

[0041] In operation, the communication device 600 provides functionality required for sensing by a proxy. For example, the communication device 600 may be an SBP initiator. The circuit 614 (e.g., at least one transmit signal generator 608 of the circuit 614) may be configured to generate a request frame. The request frame indicates conditions used by the second communication device (e.g., an SBP responder) to select one or more links each associated with one or more third communication devices (e.g., a sensing responder). The at least one wireless transmitter 602 may then transmit the request frame to the second communication device to request the second communication device to perform measurements on the one or more links. The at least one wireless receiver 604 may then receive a report frame including one or more reports of measurements corresponding to the one or more links from the second communication device.

[0042] In one embodiment, the at least one radio receiver 604 further receives a response frame from the second communication device including information identifying each of the one or more links prior to receiving a report frame including one or more reports of measurements corresponding to the one or more links from the second communication device.

[0043] In another embodiment, the at least one wireless receiver 604 further receives a validation request frame requesting validation information indicating that the communication device 600 is authorized to receive one or more reports. The circuit 614 (e.g., each of the at least one receive signal processor 610 and the at least one transmit signal generator 608 of the circuit 614) may be configured to process the validation request frame and generate a validation response frame including the validation information. The at least one wireless transmitter 602 may then transmit the validation response frame.

[0044] The communications device 600 may be a sensing SBP responder, and the at least one wireless receiver 604 may receive a request frame from a first communications device (e.g., an SBP initiator) indicating conditions for selecting one or more links each associated with one or more third communications devices (e.g., a sensing responder). The circuit 614 (e.g., the at least one transmit signal generator 608 of the circuit 614) may be configured to generate a report frame including a report of one or more measurements corresponding to the one or more links. The at least one wireless transmitter 602 may then transmit the report frame to the first communications device.

[0045] In one embodiment, the circuit 614 (e.g., the at least one transmit signal generating unit 608 of the circuit 614) may be configured to generate a setup request frame for each of the one or more third communication devices, the setup request frame including an identifier or address of the communication device 600, to set up measurements for each of the one or more third communication devices. The at least one wireless transmitter unit 602 may then transmit the setup request frame to the first communication device.

[0046] In another embodiment, the at least one wireless receiver 604 may receive a validation request frame from one of the one or more third communication devices to request validation information indicating that the first communication device is authorized to receive measurement reports from one of the one or more third communication devices. The at least one wireless transmitter 602 may then transmit the validation request frame to the communication device 600. The at least one wireless receiver 604 may then further receive a validation response frame including the validation information from the communication device 600, and the at least one wireless transmitter 602 may then transmit the validation response frame to one of the one or more third communication devices.

[0047] In yet another embodiment, the circuit 614 (e.g., at least one transmit signal generating unit 608 of the circuit 614) may be configured to assign a different setup identifier to each of the one or more links, and generate a response frame after receiving a request frame including the different setup identifiers assigned to each of the one or more links. The report frame includes information of the different setup identifiers that identify each of the one or more links corresponding to the reporting of one or more measurements.

[0048] FIG. 7 shows a flow chart 700 illustrating a communication method implemented by a first communication device, such as an SBP initiator, according to various embodiments of the present disclosure. In step 702, a step is performed of generating a request frame indicating conditions to be used by a second communication device (e.g., an SBP responder) to select one or more links each associated with one or more third communication devices (e.g., a sensing responder). In step 704, a step is performed of transmitting a request frame to the second communication device to request the second communication device to perform measurements of the one or more links. In step 706, a step is performed of receiving a report frame from the second communication device including one or more reports of measurements corresponding to the one or more links.

[0049] 8 shows a flow chart 800 illustrating a communication method implemented by a second communication device, such as an SBP responder, according to various embodiments of the present disclosure. In step 802, a step of receiving a request frame from a first communication device (e.g., an SBP initiator), the request frame indicating conditions for selecting one or more links, each of which is bound to one or more third communication devices, is performed. In step 804, a step of generating a report frame is performed, the report frame including a report of one or more measurements corresponding to the one or more links is performed. In step 806, a step of transmitting the report frame to the first communication device is performed.

[0050] The following paragraphs describe a first embodiment of the present disclosure for a proxy sensing procedure in which a non-AP STA indicates conditions for an AP to select one or more other non-AP STAs or links.

[0051] According to the first embodiment, during SBP setup, the SBP initiator (non-AP STA) specifies in the SBP request the attributes (e.g., sampling rate, report type, etc.) and information of the basic sensing operation as conditions to help the SBP responder (AP) select the STA or link. The SBP responder then determines / selects the STA / link to be used for sensing measurement based on the conditions (i.e., attributes and information).

[0052] FIG. 9 shows a flowchart 900 outlining a procedure of proxy sensing between an AP and three non-AP STAs (STA1, STA4, STA3) according to the first embodiment of the present disclosure. FIG. 10 shows a flowchart 1000 illustrating a detailed procedure flow of the proxy sensing procedure between an AP and three non-AP STAs in FIG. 9. FIG. 11 shows a schematic diagram 1100 illustrating the connection between the AP and three non-AP STAs in FIG. 9. The AP first uses a beacon / probe response frame to advertise the AP's capability to support enhanced client discovery and basic information about the associated non-AP STAs (e.g., number / number of associated STAs, etc.). STA1 may perform basic SBP discovery and discover the AP's support for SBP function. Then, STA1 may select the AP as its SBP responder.

[0053] STA1 may then initiate an extended client discovery procedure by sending a protected client discovery query frame to request the AP to provide a list of non-AP STAs (associated non-AP STAs and, optionally, non-associated non-AP STAs). The AP sends a protected client discovery response frame containing the requested list of non-AP STAs and, optionally, their respective neighboring STAs, completing the extended client discovery procedure. In this extended client discovery procedure, the SBP initiator discovers information of the AP and potential sensing responders. Specifically, the AP already has basic information of associated STAs, such as the STAs' operating channel, sensing capabilities, and R2R sensing capabilities. The SBP initiator (STA1) can obtain such information from the AP using a Level 1 client discovery query. Although not shown in the figure, when receiving a request from an SBP initiator (or even the SBP initiator itself), the AP may collect other relevant information from its associated STAs, such as information about the STA's neighboring STAs, including the STA's location / position, RSSI (or propagation loss) to / from the STA (which represents the distance between the STA and the AP), and link metrics. This allows the SBP initiator to obtain such relevant information about the AP's associated STAs (and their neighboring STAs) from the AP using a Level 2 client discovery query. Based on the above information, the SBP initiator can select one or more APs as SBP responders as well as one or more non-AP STAs as target sensing responders for the SBP procedure.Alternatively, for example, if the AP does not support Extended Client Discovery, or in addition to the information collected via Extended Client Discovery, the SBP initiator may also use information received via other means (e.g., IP / MAC addresses provided by a higher layer application) to select an SBP responder and a sensing responder for the SBP procedure.

[0054] Alternatively, the SBP initiator may initially request measurements from "all / many" available links, but later select a subset of links that are most suitable for the sensing application in subsequent SBP requests. Link selection may be based on statistical analysis of sensing measurement reports for the links, e.g., links whose CSI feedback is less likely to change relative to the needs of the sensing application may be omitted in subsequent SBP requests.

[0055] The SBP initiator (STA1) may be associated with an AP (SBP responder), in which case it is assumed that the normal authentication / association procedure with the AP has already been completed and a security association (SA) has already been set up, for example, via a 4-way handshake, before the initiation of the SBP request. Alternatively, the SBP initiator (STA1) may not be associated with an AP, in which case it is assumed that the security associated with the AP has already been set up, for example, via a Pre-Association Security Negotiation (PASN) via a 3-way handshake, before the initiation of the SBP request.

[0056] STA1 discovers an AP through a client discovery procedure and selects the AP as an SBP responder. Then, it initiates an SBP procedure and requests the AP to be a proxy sensing initiator on its behalf by sending a protected SBP request frame containing link / measurement parameters related to SBP links and measurement attributes, such as a minimum Received Signal Strength Indicator (RSSI) or Received Channel Power Indicator (RCPI), and the number of measurement links. Based on the link / measurement parameters, the AP then determines three STAs / links that are more relevant for sensing measurements (in this case, the I2R link associated with STA4, the I2R link associated with STA3, and the R2R link between STA4 and STA3), and initiates sensing session setup and sensing measurement setup with the selected STAs (STA4, STA3) by sending a protected sensing measurement setup request frame to the selected STAs. In this embodiment, the same measurement setup identifier (ID) is assigned to all different measurement links for the SBP procedure (e.g., the I2R link between the AP and the STA, and the R2R link between STA4 and STA3). STA4, STA3 (sensing responder) that receives the protected sensing measurement setup request frame then sends a protected sensing measurement setup response frame to the AP (SBP responder or proxy sensing initiator) indicating a successful sensing measurement setup.

[0057] The AP then sends a protected SBP response frame to indicate the success of the setup with its sensing responder, and also indicates the measurement setup ID selected for the SBP procedure to the SBP initiator (STA1) to complete the SBP setup.

[0058] Subsequently, the AP performs sensing measurement instances with STA4 and STA3 by first transmitting an I2R measurement PPDU (e.g., sensing NDP) to STA4 and STA3. In response, STA4 and STA3 measure their respective channels based on receiving the I2R measurement PPDU and transmit their measurement reports if requested. The measurement report includes the assigned measurement setup ID "1". After collecting the measurement reports on its own links, the AP consolidates the measurement reports and transmits a protected SBP report frame to STA1 including the measurement reports of the I2R links with STA4 and STA3. The report frame includes link information such as STA ID or other ID that can be used to identify the I2R measurement link. Alternatively or additionally, R2R measurements and R2R link reports may also be performed during the same measurement instance (measurement instance ID 1). In this case, STA4 transmits an R2R measurement PPDU (e.g., sensing NDP) to STA3, and STA3 transmits a measurement report to the AP in response. The measurement report includes the assigned measurement setup ID "1". Upon receiving the measurement report, the AP then transmits a protected SBP report frame to STA1 that includes the measurement report of the R2R link between STA4 and STA3. Similarly, the SBP report frame includes link information such as the STA ID or other IDs that can be used to identify the R2R measured link.

[0059] Alternatively, as shown in Figure 9, the AP may perform measurements on different links / STAs in different measurement instances (different measurement instance IDs but the same measurement setup ID), e.g., perform a sensing measurement with STA3 under measurement instance ID "1" in the first measurement instance, and then perform a sensing measurement with STA4 under measurement instance ID "2" in the second measurement instance. The AP then sends an SBP report frame to STA1 including the measurement reports of STA4 and STA3 received in the different measurement instances. Similarly, the report frame includes link information such as STA ID or other ID that can be used to identify the measured link.

[0060] Finally, STA1 may initiate the termination of the SBP procedure by sending an SBP end frame (not shown) to the AP after the SBP procedure. The AP then performs the termination of sensing measurement and the termination of the sensing session for the sensing measurement setup ID corresponding to the SBP procedure together with STA4 and STA3.

[0061] FIG. 12 illustrates an example format of an Extended Capability Element 1200 used for basic discovery according to one embodiment of the present disclosure. The Extended Capability Element 1200 is used to indicate the capabilities of a STA (AP or non-AP) and support for specified services and communication functions. It has an Element ID field, a Length field, and an Extended Capabilities field. The Extended Capabilities field includes a WLAN Sensing subfield, an SBP subfield, an SBP R2R subfield, a Level 1 Enhanced Client Discovery subfield, and a Level 2 Enhanced Client Discovery subfield. The SBP subfield indicates that the AP is capable of providing proxy sensing services with associated STAs. The SBP R2R indicates that the AP is capable of providing proxy sensing services in an R2R link with its associated STAs. The Level 1 and Level 2 Enhanced Client Discovery subfields indicate that the AP / non-AP STAs can perform Level 1 and Level 2 enhanced client discovery. For Level 1 enhanced client discovery, the AP can provide a list of non-AP STAs (associated non-AP STAs and, optionally, non-associated non-AP STAs), and for Level 2 enhanced client discovery, the AP can provide detailed information of neighboring clients / devices located within the wireless range of a specified non-AP STA (associated non-AP STAs or non-associated non-AP STAs).

[0062] In the present disclosure, an SBP initiator and an SBP responder exchange SBP request / response / termination frames to set up an SBP procedure if no security association (SA) exists between them. If so, they exchange protected SBP request / response frames. According to the first embodiment of the present disclosure, exemplary formats of an SBP request frame 1300 and a protected SBP request frame 1310 are shown in FIG. 13A and FIG. 13B, respectively. The SBP request frame 1300 includes a MAC Header (Frame Control field, Duration field, Recipient Address (RA) field, Transmitter Address (TA) field), a Category field set to "Public", a Public Action field set to "SBP Request", a Dialog Token field, an SBP parameter element, and a Frame Checking Sequence (FCS) field. The SBP protection frame 1310 includes a MAC header (Frame Control, Duration, RA and TA fields), a Category field set to "Protected Dual of Public Action", a Public Action field set to "Protected SBP Request", a Dialog Token field, an SBP Parameter Elements field, and an FCS field.

[0063] 14A and 14B show exemplary formats of an SBP response frame 1400 and a protected response frame 1410, respectively, according to a first embodiment of the present disclosure. The SBP response frame 1400 includes a MAC header (Frame Control, Duration, RA, and TA fields), a Category field set to "Public", a Public Action field set to "SBP Response", a Dialog Token field, a Status Code field, a Measurement Setup ID field, an SBP Parameters Element field, an SBP Link Info Element field, and an FCS field. The protected SBP response frame 1410 includes a MAC header (Frame Control, Duration, RA, and TA fields), a Category field set to "Protected Public Action Dual", a Public Action field set to "Protected SBP Response", a Dialog Token field, a Status Code field, a Measurement Setup ID field, an SBP Parameter Elements field, an SBP Link Information Elements field, and an FCS field.

[0064] The Measurement Setup ID field is set to a Measurement Setup ID value that uniquely identifies the SBP procedure and all measurement links corresponding to the SBP procedure. The Measurement Setup ID field is present in the SBP response frame 1400, 1410 only if the Status Code field indicates "success".

[0065] 15 shows an example format of an SBP parameter element field 1500 in the SBP request frame 1300, 1310 / SBP response frame 1400, 1410 of FIGS. 13A-14B. The SBP parameter element field includes an Element ID field, a Length field, an Element ID Extension field, and an SBP parameters field. The SBP parameters field includes a Link Parameters subfield, a Measurement Parameters subfield, and a Report Parameters subfield that specify attributes related to the link being measured, the measurement PPDU, and the SBP report, respectively.

[0066] The Link Parameters subfield includes an Include SBP Initiator bit, an Include R2R bit, a Minimum RSSI / RCPI subfield, and a Number of Measurement Links subfield. The Include SBP Initiator bit is set to 1, indicating a request to include the SBP initiator as one of the sensing responders. Thus, measurement reports on the links to which the SBP initiator is attached are also measured and included in the SBP report frame. The Include R2R bit is set to 1 to indicate that R2R links may be taken into account. The Minimum RSSI / RCPI subfield indicates that the average of the RSSI or RCPI observed for frames transmitted on the selected links is expected to be above the indicated level. The Number of Links subfield indicates the number of links used for sensing measurements.

[0067] The Measurement Parameters subfield includes an NDP Type subfield, an NDP Bandwidth subfield, and a Sampling Rate subfield. The NDP Type subfield indicates the NDP type or format (e.g., High Efficiency (HE), Extremely High Throughput (EHT), or Ranging) used to measure the channel. The NDP Bandwidth subfield indicates the channel bandwidth of the NDP used to measure the channel. The Sampling Rate subfield indicates how often the measurements are made, i.e., how often the sensing measurements are performed in terms of measurements per Hz or per second.

[0068] The Reporting Parameters subfield includes the Measurement Report Type subfield, the Report Frequency subfield, and the Channel State Information (CSI) Variation Threshold subfield. The Measurement Report Type subfield indicates the type of sensing measurement report used during the SBP reporting procedure. The Report Frequency subfield indicates the frequency of sending the SBP report, i.e., how often the SBP report is sent in terms of Hz or transmissions per second. The CSI Variation Threshold subfield indicates a number between 0 and 1 that corresponds to a threshold used to determine if the change in the measured CSI is large enough for the AP to generate an SBP report.

[0069] FIG. 16 illustrates an example format of an SBP Link Information Element field 1600 in the SBP response frame 1400, 1410 of FIG. 14A and FIG. 14B according to an embodiment. The SBP Link Information Element field includes an Element ID field, a Length field, an Element ID Extension field, and an SBP Link Info field. The SBP Link Info field includes a Link Info Count (N) subfield and one or more Link Information fields corresponding to one or more links. The Link Info Count (N) subfield indicates the number of links (Link Information subfields) present in the SBP Link Info field. Each Link Info subfield includes a STA2 Present subfield, a STA1 ID subfield, and a STA2 ID subfield (if the STA2 Present subfield is set to 1). In the case of an I2R or R2I link to which the SBP responder itself is attached, the STA2 Presence subfield is set to 0 and the STA1 ID subfield indicates the STA ID (e.g., MAC address or Associated Identifier (AID)) of the STA associated with the other end of the link. In the case of an R2R link, the STA2 Presence subfield is set to 1 and the STA1 and STA2 ID subfields indicate the STA IDs (e.g., MAC addresses or AIDs) of the two STAs associated with both ends of the R2R link. Alternatively, instead of the STA ID, a unique link ID (assigned during sensing measurement setup for the SBP procedure) for each measured link may be included in the Link Information subfield. The SBP initiator uses the link ID to identify the measured link in subsequent frames.

[0070] Regarding SBP reporting, the sensing measurement results obtained in the WLAN sensing procedure resulting from an SBP request are reported by the SBP responder to the SBP initiator in a protected SBP report frame, which is either constructed by the SBP responder (AP) itself (if the AP is a sensing receiver) or by adding a link information field (shown in Figure 16) and updating the resulting Report Length field in each sensing measurement report field sent by the sensing responder on the link.

[0071] FIG. 17 illustrates an exemplary format of an SBP report frame 1700 according to the first embodiment of the present disclosure. The SBP report frame 1700 includes a MAC header (Frame Control, Duration, RA, and TA fields), a Category field set to “Protected Sensing”, an Action field set to “Protected SBP Report”, a Dialog Token field, a Sensing Measurement Report List field, and an FCS field. The Sensing Measurement Report List field includes one or more Sensing Measurement Report fields corresponding to one or more links. Each Sensing Measurement Report field includes a Report Length field, a Measurement Setup ID field, a Measurement Instance ID field, a Sensing Measurement Time field, a Sensing Measurement Report Type field, a Sensing Measurement Control field, a Sensing Measurement Feedback field, and a Link Information field. The Report Length field indicates the length of the Sensing Measurement Report field. If a Link Information field is added, the Report Length field should also be updated accordingly. The Measurement Setup ID field indicates the Measurement Setup ID value corresponding to the SBP procedure. The Measurement Instance ID field identifies the measurement instance for which the sensing measurement is performed. The Sensing Measurement Time field indicates the measurement timestamp at which the measurement was performed by the sensing receiver (responder).The sensing measurement control field includes an Nc Index subfield, an Nr Index subfield, a Bandwidth (BW) subfield, a Number of Groups (NG) subfield, a Remaining Feedback Segments subfield, and a First Feedback Segment subfield. The sensing measurement feedback includes a sensing measurement result, such as CSI or partial CSI. The link information in FIG. 16 includes a STA2 Present subfield, a STA1 ID subfield, and a STA2 ID subfield (when the STA2 Present subfield is set to 1 to indicate an R2R link). The STA1 and STA2 ID subfields include the IDs (e.g., MAC addresses or AIDs) of the sensing responders and identify the links corresponding to the sensing measurement report. Alternatively, a unique link ID may be assigned for each measurement link and included in the link information subfield, instead of a STA ID.

[0072] According to the first embodiment of the present disclosure, Figures 18A and 18B show exemplary formats of an SBP End frame 1800 and a protected SBP End frame 1810, respectively. The SBP End frame 1800 includes a MAC header (Frame Control, Duration, RA, and TA fields), a Category field set to "Public", a Public Action field set to "SBP End", a Measurement Setup ID field, and an FCS field. The Protected SBP End frame 1810 includes a MAC header (Frame Control, Duration, RA, and TA fields), a Category field set to "Protected Public Action Dual", a Public Action field set to "Protected SBP End", a Measurement Setup ID field, and an FCS field. The Measurement Setup ID field is set to a Measurement Setup ID value assigned by the SBP responder (AP) corresponding to the SBP procedure being terminated.

[0073] FIG. 19 shows a flowchart 1900 illustrating communication between an SBP initiator (non-AP STA) and an SBP responder (AP), such as communication between the Station Management Entity (SME) and MAC subLayer Management Entity (MLME) of the SBP initiator and the SBP responder for sensing by a proxy according to the first embodiment of the present disclosure. The MLME-SBP.request primitive is issued by the MAC sublayer to request the SME of the SBP initiator to send an SBP request frame to the peer STA (SBP responder). Upon receipt of this primitive, the MLME of the SBP initiator constructs an SBP request frame and causes it to be sent to the MAC address of the peer STA (SBP responder). The MLME-SBP.request primitive and its primitive parameters are shown as follows:

[0074] MLE-SBP.request( PeerSTAAddress, SBPParameters )

[0075] Table 1 shows details of the primitive parameters included in the MLME_SBP_request primitive. [Table 1]

[0076] The MLME-SBP.indication primitive is issued by the MAC sublayer to notify the SME of an SBP responder of the receipt of an SBP request frame from a peer STA (SBP initiator). On receipt of this primitive, the SME initiates the SBP procedure on behalf of the peer STA. The MLME-SBP_indication primitive and its primitive parameters are denoted as follows:

[0077] MLME-SBP.indication( PeerSTAAddress, SBPParameters )

[0078] Table 2 shows details of the primitive parameters included in the MLME_SBP.indication primitive. [Table 2]

[0079] The MLME-SBP.response primitive is issued by the SBP responder's SME to the MAC sublayer in response to an MLME-SBP.indication and a request to send an SBP response frame to the peer STA (SBP initiator). On receipt of this primitive, the SBP responder's MLME constructs an SBP response frame and ensures that it is sent to the MAC address of the peer STA. The MLME-SBP.response primitive and its primitive parameters are shown below:

[0080] MLME-SBP.response( PeerSTAAddress, StatusCode, SBPParameters, MeasurementSetupID, SBPLinkInfo )

[0081] Table 3 shows details of the primitive parameters included in the MLME_SBP_response primitive. [Table 3]

[0082] The MLME-SBP.confirm primitive is issued to the MAC sublayer of the SBP initiator to the SME to notify the result of the SBP response when an SBP response is received from a peer STA (SBP responder). The MLME-SBP.confirm primitive and its primitive parameters are shown as follows:

[0083] MLME-SBP.confirm( PeerSTAAddress, StatusCode, SBPParameters, MeasurementSetupID, SBPLinkInfo )

[0084] Table 4 shows details of the primitive parameters included in the MLME-SBP.confirm primitive. [Table 4]

[0085] The MLME-SBPREPORT.request primitive is issued by the SBP responder's SME to the MAC sublayer to request the transmission of an SBP report frame to a peer STA (SBP initiator). On receipt of the primitive, the SBP responder's MLME constructs an SBP report frame and ensures that it is sent to the peer STA's MAC address. The MLME-SBPREPORT.request primitive and its primitive parameters are shown below:

[0086] MLME-SBPREPORT.request( PeerSTAAddress, SensingMeasurementReportList )

[0087] Table 5 shows details of the primitive parameters included in the MLME-SBPREPORT.request primitive. [Table 5]

[0088] The MLME-SBRREPORT.indication primitive is issued by the MAC sublayer to notify the SME of the SBP initiator of the reception of an SBP report frame from a peer STA (the SBP responder). The MLME-SBRREPORT.indication primitive and its primitive parameters are shown below.

[0089] MLME-SBPREPORT.indication( PeerSTAAddress, SensingMeasurementReportList )

[0090] Table 6 shows details of the primitive parameters included in the MLME-SBPREPORT.request primitive. [Table 6]

[0091] The MLME-SBPREPORT.confirm primitive is issued by the MAC sublayer to the SME of the SBP responder to notify the result of the request for the transmission of an SBP report frame. The MLME-SBPREPORT.confirm primitive and its primitive parameters are shown below.

[0092] MLME-SBPREPORT.confirm( PeerSTAAddress, StatusCode, )

[0093] Table 7 shows details of the primitive parameters included in the MLME-SBPREPORT.confirm primitive. [Table 7]

[0094] The MLME-SBPTERMINATION.request primitive is issued by the SME to the MAC sublayer to request the transmission of an SBP termination frame to the peer STA. On receipt of this primitive, the MLME constructs an SBP termination frame and causes it to be sent to the peer MAC address.

[0095] MLME-SBPTERMINATION.request( PeerSTAAddress, )

[0096] Table 8 shows details of the primitive parameters included in the MLME-SBPTERMINATION.request primitive. [Table 8]

[0097] The MLME-SBPTERMINATION.indication primitive is issued by the MAC sublayer to the SME to acknowledge receipt of an SBP termination frame from a peer STA.

[0098] MLME-SBPTERMINATION.indication( PeerSTAAddress, )

[0099] Table 9 shows details of the primitive parameters included in the MLME-SBPTERMINATION.indication primitive. [Table 9]

[0100] The MLME-SBPTERMINATION.confirm primitive is issued by the MAC sublayer to the SME to inform it of the result of the request to send an SBP termination frame.

[0101] MLME-SBPTERMINATION.confirm( PeerSTAAddress, StatusCode, )

[0102] Details of the primitive parameters included in the MLME-SBPTERMINATION.confirm primitive are shown in Table 10. [Table 10]

[0103] In FIG. 19, the SBP end frame is sent by the SBP initiator, but it can also be sent by the SBP responder, in which case the direction of the corresponding MLME primitive is reversed.

[0104] The following paragraphs describe a second embodiment of the present disclosure for a proxy sensing procedure in which a non-AP STA indicates the conditions and target STA or link information for the AP to select one or more other non-AP STAs or links.

[0105] FIG. 20A shows a flowchart 2000 outlining a procedure of proxy sensing between an AP and three non-AP STAs (STA1, STA2, STA3) according to a second embodiment of the present disclosure. FIG. 21 shows a flowchart 2100 showing a detailed procedure flow of the proxy sensing procedure between the AP and three non-AP STAs in FIG. 20A. The AP first uses a Beacon / Probe Response frame to announce the AP's capability to support enhanced client discovery and basic information about associated non-AP STAs (e.g., number / number of associated STAs, etc.). STA1 may perform basic SBP discovery and discover the AP's support for SBP function. Then, STA1 may select the AP as its SBP responder.

[0106] STA1 (SBP initiator) may then start the enhanced client discovery procedure by sending a protected client discovery query frame requesting the AP (SBP responder) to provide a list of non-AP STAs (associated non-AP STAs and, optionally, non-associated non-AP STAs). The AP sends a protected client discovery response frame containing the requested list of non-AP STAs and, optionally, their respective neighboring STAs, completing the enhanced client discovery procedure.

[0107] The SBP initiator (STA1) may be associated with an AP (SBP responder), in which case it is assumed that the normal authentication / association procedures with the AP have already been completed and that a security association (SA) has already been set up, e.g., via a 4-way handshake, before the initiation of the SBP request. Alternatively, the SBP initiator (STA1) may not be associated with an AP, in which case it is assumed that the security associated with the AP has already been set up, e.g., through a pre-association security negotiation (PASN) via a 3-way handshake, before the initiation of the SBP request.

[0108] STA1 discovers AP, STA2 and STA3 from the discovery procedure and selects AP as the SBP responder. Then, it initiates the SBP procedure and requests the AP to be a proxy sensing initiator on its behalf by sending a protected SBP request frame containing link / measurement parameters and information related to SBP link and measurement attributes such as minimum RSSI / RCPI and the number of measurement links. Unlike the SBP procedure described in the first embodiment, in this second embodiment, the SBP request frame also contains information of target device parameters such as location, coverage information and STA ID of one or more specific target sensing responders. Based on the link / measurement parameters and target device parameters, the AP then determines three STAs / links (in this case, the I2R link associated with STA2, the I2R link associated with STA3, and the R2R link between STA2 and STA3) that are more relevant for sensing measurements based on the parameters and information of the target sensing responder, and initiates sensing session setup and sensing measurement setup with the selected STAs (STA2, STA3) by sending protected sensing measurement setup request frames to the selected STAs.

[0109] In this second embodiment, a unique Measurement Setup ID (MSID) is assigned to each measurement link for the SBP procedure. For example, the I2R link between the AP and STA3 is assigned MSID "1", the link between the AP and STA2 is assigned MSID "2", and the R2R link between STA2 and STA3 is assigned MSID "3". STA2, STA3 (sensing responder) receiving the protected sensing measurement setup request frame then replies to the AP (SBP responder or proxy sensing initiator) with a protected sensing measurement setup response frame indicating successful sensing measurement setup.

[0110] The AP then sends a protected SBP response frame back to the SBP initiator (STA1) to indicate successful setup along with its sensing responders and the measurement setup ID selected for the SBP procedure and assigned to the measurement link, completing the SBP setup.

[0111] Then, the AP performs a sensing measurement instance with STA2 and STA3 by first sending an I2R measurement PPDU (e.g., sensing NDP) to STA2 and STA3. In response, STA2 and STA3 measure their respective channels based on receiving the I2R measurement PPDU and send their respective measurement reports if requested. The measurement reports include their respective measurement setup IDs "1" and "2". After collecting the measurement reports on their own links, the AP consolidates the measurement reports and sends a protected SBP report frame to STA1 including the measurement reports of the I2R links between the AP and STA2 and STA3. The measurement setup IDs are included in the measurement reports in the SBP report frame to identify the measurement links, respectively. Alternatively or additionally, R2R measurements and R2R link reports may also be performed during the same measurement instance (measurement instance ID 1). In this case, STA2 sends an R2R measurement PPDU (e.g., sensing NDP) to STA3, and STA3 sends a measurement report to the AP in response. The measurement report includes its measurement setup ID "3". Upon receiving the measurement report, the AP then sends a protected SBP report frame to STA1 including a measurement report of the R2R link between STA2 and STA3. The measurement setup ID is included in the measurement report in the SBP report frame to identify the measurement link, respectively.

[0112] Alternatively, as shown in FIG. 20A, the AP may perform measurements on different links / STAs in different measurement instances (different measurement instance IDs but the same measurement setup ID), e.g., perform a sensing measurement with STA3 under measurement instance ID “1” in the first measurement instance, and then perform a sensing measurement with STA2 under measurement instance ID “2” in the second measurement instance. The AP then sends an SBP report frame to STA1 including measurement reports of its I2R links with STA2 and STA3 received in different measurement instances. The measurement setup ID is included in the measurement report in the SBP report frame to identify the I2R and R2R measurement links, respectively.

[0113] Finally, STA1 may initiate the termination of the SBP procedure by sending an SBP end frame (not shown) to the AP after the SBP procedure. The AP then performs, together with STA2 and STA3, the termination of the sensing measurement and the termination of the sensing session for the sensing measurement setup ID corresponding to the SBP procedure.

[0114] FIG. 22 is an exemplary visualization of an extended client discovery result. The result of the extended client discovery corresponds to the links between devices located in the floor plan of the floor, as shown in FIG. 5. Such a visualization may be displayed on the screen of a laptop, a smartphone, or any electronic device. In this example, the SBP initiator (STA8) performs a level 1 client discovery and displays only a list of AP / AP MLDs (in this case, four different APs (AP1, AP2, AP3, AP4)). Each AP sends their discovery results consisting of a list of STAs associated with the AP, along with their basic information, to the SBP initiator. They may be sorted in descending order according to link quality. Optionally, a list of unassociated STAs (and / or MLDs) known to the AP is also provided by the AP. In this example, AP1 provides information for STA8, STA5, and phone1, AP2 provides information for STA7 and STA1, AP4 provides information for STA4 and STA6, and AP3 provides information for STA2 and STA3. The SBP initiator may additionally or alternatively perform a level 2 client discovery. This level 2 client discovery may be triggered by selecting in a specific STA or non-AP MLD. In this example, STA-5 is selected, and the SBP initiator performs a level 2 client discovery with AP1 for STA-5. A client discovery query frame including STA-5' ID (e.g., MAC address) is sent to AP1. Thus, AP1 provides not only the information of STA-5, but also the information of its neighboring APs, STAs (in this case, STA5, STA8 (the SBP initiator itself)), Phone1, STA1, AP2, AP4, and STA4) located within the wireless range of STA-5, as shown in block 2202. The result can then be used to select a sensing responder for SBP procedure measurement.

[0115] As part of the enhanced client discovery, the SBP initiator can also discover the location of APs (in addition to the location of non-AP STAs). The location information may be obtained via GPS (if outdoors) or precision timing measurements and / or ranging (if indoors), etc. The location information of the APs (along with other information such as supported capabilities) may be used by the SBP initiator to select an appropriate AP to act as an SBP responder. If the STA information field in the client discovery response frame contains information for a DMG (Directional Multi-Gigabit, i.e., 802.11ad) STA or an EDMG (Enhanced Directional Multi-Gigabit, i.e., 802.11ay) STA, the STA information field may also contain a Sector Select subfield containing the value of the Sector ID subfield of the SSW field in the frame that was received with the best quality in the previous sector sweep. The Sector ID subfield indicates the sector number to which the frame containing this SSW field is transmitted. When selecting a sensing responder STA from among the DMG / EDMG STAs, the AP may take into consideration and use the sector number information.

[0116] 23 illustrates an example format of an SBP parameter element field of an SBP request frame according to the second embodiment of the present disclosure. The SBP parameter element field 2300 includes an Element ID field, a Length field, an Element ID Extension field, and an SBP parameters field. Unlike the SBP parameter element field illustrated in FIG. 15 for the first embodiment, the SBP parameters field includes additional Target Device Parameter subfield, Link Parameter subfield, Measurement Parameter subfield, and Report Parameter subfield, which specify attributes related to the target STA / link, the measured link, the measurement PPDU, and the SBP report, respectively.

[0117] The Link Parameters subfield, the Measurement Parameters subfield, and the Reporting Parameters subfield are the same as those described in FIG. 15. The Target Device Parameters subfield includes a Target Device Control field, a Device Location Info field, a Coverage Info field, and one or more Target Device Info fields. The Target Device Control field includes a Device Type subfield, a Device Location Info Present subfield, a Coverage Info Present subfield, and a Target Device Count (N) subfield. The Device Type subfield specifies device type restrictions for sensing responders.

[0118] Table 11 shows the various device types that correspond to the Device Type subfield values. [Table 11]

[0119] The Device Location Information Present and Coverage Information Present subfields indicate the presence of corresponding fields in the Target Device Parameters subfield. The Number of Target Devices (N) subfield indicates the number of target device information fields in the Target Device Parameters subfield.

[0120] The Device Location Information field specifies the location of the device and uses the location as a center to determine the coverage area or radio range extended from the location. The Coverage Information field includes a Coverage Radius subfield and a Coverage Sector Bitmap subfield. The Coverage Radius subfield specifies the radius (presented, for example, by RSSI / RCPI level (dBm) or as distance (m)) of the coverage area with the device location specified in the Device Location Information field. The Coverage Sector Bitmap subfield indicates a segment or region for the device location.

[0121] The Device Location Information field contains information about the location where the target STA should be located. For example, the field may contain a Device Location Information Body field, as described in 9.4.1.56 of 802.11-2020. The Device Location Information Body field contains Location Configuration Information (LCI), including latitude, longitude, and altitude information. Together with the Coverage Information field, the SBP initiator can specify a coverage area (with the location indicated in the Device Location Information field). The SBP initiator requests the AP (SBP responder) to select a target sensing responder within this coverage area. If the Device Location Information field is not present but the Coverage Information field is present, the location of the SBP responder (AP) is considered as the center of the target coverage area.

[0122] Table 12 shows the various sectors that are indicated by bits in the coverage sector bitmap. [Table 12]

[0123] Each target device information field within the target device parameters subfield specifies a target link and has a STA2 Presence subfield, a STA1 ID subfield, and a STA2 ID subfield. For an I2R or R2I link, the STA2 Presence subfield is set to 0 and the STA1 ID subfield indicates the STA ID (e.g., MAC address, association identifier (AID), or unassociated ID (UID)) of the STA associated with the link, while the SBP responder is understood to be attached to the other end of the link. For an R2R link, the STA2 Presence subfield is set to 1 and the STA1 ID and STA2 ID subfields indicate the STA IDs (e.g., MAC addresses or AIDs) of the two STAs associated with the R2R link. Alternatively, a unique link ID may be assigned for each measurement link and included in the link information subfield, rather than a STA ID.

[0124] Although not shown in the figure, other information about the target device, such as device name, PHY version (HT / VHT / HE / EHT, etc.), supported features (WLAN sensing supported, precise timing measurement (FTM) supported, etc.), may also be included in the target device parameters field.

[0125] According to the second embodiment of the present disclosure, the SBP initiator provides the specified target device parameters in the target device parameters subfield frame in addition to the link / measurement parameters in the SBP parameter element field in the SBP request to the SBP responder (AP), and the SBP responder (AP) uses the provided target device parameters and link parameters to select the STA / link to be used for the SBP sensing measurement. For example, if the device location information field and the coverage information field are included, the AP may select the STA that is located within the specified sector of the coverage area and meets the link parameters (e.g., minimum RSSI / RCPI). Additionally or alternatively, if the target device information field is included, the AP directly selects the STA that is indicated to meet other parameters such as the link parameters. Then, the SBP responder (AP) acts as a sensing initiator and performs the sensing session setup and the sensing measurement setup with the selected STA (sensing responder) using a unique measurement setup ID for each measurement link.

[0126] 24A and 24B show exemplary formats of an SBP response frame 2400 and a protected response frame 2410, respectively, according to a second embodiment of the present disclosure. The SBP response frame 2400 includes a MAC header (frame control, duration, RA, and TA fields), a category field set to "public", a public action field set to "SBP response", a dialog token field, a status code field, an SBP parameter element field, an SBP link information element field, and an FCS field. The protected SBP response frame 2410 includes a MAC header (frame control, duration, RA, and TA fields), a category field set to "protected public action dual", a public action field set to "protected SBP response", a dialog token field, a status code field, an SBP parameter element field, an SBP link information element field, and an FCS field. It should be noted that for the SBP procedure according to the second embodiment, the measurement setup ID is included in a different SBP link element field in the SBP response frames 2400, 2410 than in the SBP response frames 1400, 1410 shown in Figures 14A and 14B, since different measurement links are assigned different measurement setup IDs. Alternatively, a measurement setup ID field is also included in the SBP response frame itself, and a unique measurement setup ID can be assigned to represent the SBP procedure.

[0127] FIG. 25 illustrates an example format of an SBP link information element field 2500 of the SBP response frame 2400, 2410 of FIG. 24A and FIG. 24B according to an embodiment. The SBP link information element field includes an Element ID field, a Length field, an Element ID Extension field, and an SBP Link Information field. The SBP Link Information field includes a Link Information Count (N) subfield and one or more Link Information fields corresponding to one or more links. The Link Information Count (N) subfield indicates the number of links (Link Information subfields) present in the SBP Link Information field. Each Link Information subfield includes a STA2 Present subfield, a STA1 ID subfield, a STA2 ID subfield (if the STA2 Present subfield is set to 1), and a Measurement Setup ID subfield. For an I2R or R2I link, the STA2 Present subfield is set to 0, and the STA1 ID subfield indicates the STA ID (e.g., MAC address, AID, or UID) of the STA associated with the link. For an R2R link, the STA2 Present subfield is set to 1, and the STA1 and STA2 ID subfields indicate the STA IDs (e.g., MAC addresses, AIDs, or UIDs) of the two STAs associated with the R2R link. A unique Link ID for each measurement link is assigned to and included in the Measurement Setup ID subfield of the Link Information subfield.

[0128] If the setup is successful, the AP proceeds to perform a sensing measurement instance on the selected link based on the attributes indicated in the SBP request and, if applicable, collects sensing measurement reports from sensing responders.

[0129] Regarding SBP reporting, the sensing measurement results obtained in the WLAN sensing procedure resulting from an SBP request are reported by the SBP responder to the SBP initiator in a protected SBP report frame, which is either constructed by the SBP responder (AP) itself (if the AP is a sensing receiver) or by adding a link information field (shown in Figure 16) and updating the resulting report length field in each sensing measurement report field sent by the sensing responder on the link.

[0130] FIG. 26 illustrates an exemplary format of an SBP report frame 2600 according to the second embodiment of the present disclosure. The SBP report frame 2600 includes a MAC header (frame control, duration, RA, and TA fields), a category field set to “protected sensing”, an action field set to “protected SBP reporting”, a dialog token field, a sensing measurement report list field, and an FCS field. The sensing measurement report list field includes one or more sensing measurement report fields corresponding to one or more links. Each sensing measurement report field includes a report length field, a measurement setup ID field, a measurement instance ID field, a sensing measurement time field, a sensing measurement report type field, a sensing measurement control field, a sensing measurement feedback field, and a link information field. The report length field indicates the length of the sensing measurement report field. If a link information field is added, the report length field should also be updated accordingly. The measurement setup ID field indicates a measurement setup ID value corresponding to a measurement setup assigned and initiated by the AP. The measurement setup ID uniquely identifies the link corresponding to the sensing measurement report from other sensing measurement reports. The measurement instance ID field identifies the measurement instance at which the sensing measurement is performed. The sensing measurement time field indicates the measurement timestamp at which the measurement is performed by the sensing receiver (responder). The sensing measurement control field includes an Nc index subfield, an Nr index subfield, a bandwidth (BW) subfield, an NG (number of groups) subfield, a remaining feedback segment subfield, and a first feedback segment subfield. The sensing measurement feedback includes the sensing measurement result, such as CSI or partial CSI. The link information in FIG. 25 includes a STA2 Present subfield, a STA1 ID subfield, and a STA2 ID subfield (if the STA2 Present subfield is set to 1 to indicate an R2R link).The STA1 and STA2 ID subfields contain the ID of the sensing responder (e.g., MAC address, AID, or UID) and identify the link corresponding to the sensing measurement report. Alternatively, instead of the STA ID, a unique link ID may be assigned for each measurement link and included in the link information subfield. In this embodiment, the link information field may be omitted because a unique measurement setup ID is assigned to identify each measurement link. In this case, instead of using a protected SBP report frame, the SBP responder may directly forward a protected sensing measurement report frame received from the STA (with the MAC header properly modified if necessary) or generated by the SBP responder itself to the SBP initiator, i.e., the sensing measurement report frame can also be used as the SBP report frame.

[0131] FIG. 27A is a schematic diagram 2700 showing a floor plan and devices located on the floor with two exemplary implementations of a proxy sensing procedure according to the second embodiment of the present disclosure. As an example, a motion detection sensing application is running on the SBP initiator (STA8) to detect the movement of a person in the office entrance / lobby area 2704. The SBP initiator performs basic client discovery and advanced client discovery, and selects AP1 and AP2 as two SBP responders, for example, based on their capabilities (e.g., SBP support) and locations, and the capabilities and locations of their associated STAs. In this example, the SBP initiator includes the following target device parameters and link parameters as target selection criteria for AP1: Device type = "Non-mobile devices only" Device location information present = 0 Coverage radius = -62dBm, Coverage sector = North and East Number of target devices (N) = 0 Include SBP initiator bit = 1 Include R2R bit = 1 Number of measured links = 3

[0132] Based on the specified target selection criteria, a target coverage area 2706 can be determined from the coverage radius parameter (since there is no device location information, the location of AP-1 is taken as the center of the target coverage area), and AP1 selects three links (AP1-STA8 link 2706, AP1-STA9 link 2707, and STA8-STA9 link 2708) for SBP measurement. Similarly, the SBP initiator also includes similar parameters as AP2 as target selection criteria and sets up an SBP with AP2 on one link (AP2-STA1 link 2708) for SBP measurement.

[0133] In another example that can be implemented as a continuation of the first example, STA8 may be implemented as a motion detection sensor and obtain sensing measurement results from three selected SBP links (AP1-STA8 link, AP1-STA9 link, STA8-STA9 link) by, for example, the SBP procedure according to the first exemplary embodiment, but may determine that the sensing measurement results on the AP1-STA9 link and the STA8-STA9 link are less disruptive (e.g., because people entering near the entrance / lobby are farther from the links). The SBP initiator (STA8) may then determine that STA5 is a better choice than STA9 for SBP measurement. STA8 then (re)initiates a new SBP setup with AP1, for example, after terminating the previous SBP setup.

[0134] The SBP initiator includes the following target device parameters and link parameters in the new SBP request frame as target selection criteria for AP1. Device Type = "All Types" Device location information exists = Coverage information exists = 0 Number of target devices (N) = 3 Include SBP initiator bit = 1 Include R2R bit = 1 Number of measured links = 3 Target device information 1,2,3=STA8,STA5;STA5,STA8 (R2R link)

[0135] The SBP initiator directly specifies the target STAs to be used as sensing responders for the SBP procedure. Based on the specified target selection criteria (i.e., target device information), AP1 selects three links (AP1-STA8 link 2706, AP1-STA5 link 2709, and STA8-STA5 link 2710) for SBP measurement.

[0136] FIG. 27B illustrates another exemplary format of an SBP request frame 2750 according to the second embodiment. In the above second example, after the SBP initiator (STA8) determines that STA5 is a better choice than STA9 for SBP measurement, instead of terminating the existing SBP procedure, the SBP initiator may also choose to make a change to the existing SBP procedure and send an SBP request frame 2750 with the Re-Setup bit field 2752 set to 1 to indicate that this is not a new SBP request, but rather a request for a change in SBP parameters. When the Re-Setup bit field 2752 is equal to 1, the Measurement Setup ID field is present in the SBP request frame and indicates the Measurement Setup ID corresponding to the SBP procedure to be re-setup. The SBP initiator includes the following target device parameters and link parameters in the SBP request frame for SBP re-setup as target selection criteria to AP1: Device Type = "All Types" Device location information exists = Coverage information exists = 0 Number of target devices (N) = 3 Include SBP initiator bit = 1 Include R2R bit = 1 Number of measured links = 3 Target device information 1,2,3=STA8,STA5;STA5,STA8 (R2R link)

[0137] Upon receiving this SBP request frame, the SBP responder (AP-1) compares the STAs specified in the target device information and finds out that the SBP initiator requests to remove the sensing responder STA-9 from the current SBP procedure and use STA-5 as the second sensing responder of the SBP procedure instead. Based on the specified target device information, AP1 sends a sensing end frame to STA-9 to end its sensing measurement setup with STA-9 in the MSID corresponding to the SBP procedure. AP1 also performs a sensing measurement setup with STA-5 and adds STA-5 as a new sensing responder for the SBP procedure corresponding to the MSID. This use of SBP request re-setup has the advantageous effect of changing SBP parameters without the need to end the SBP procedure and perform a new SBP setup.

[0138] The following paragraphs describe a third embodiment of the present disclosure for a proxy-based sensing procedure, in which a non-AP STA negotiates one SBP procedure for one measurement link at a time. Different measurement setup IDs are assigned to different measurement links for the SBP procedure. The measurement setup IDs can then be used to identify the measurement link corresponding to the sensing measurement report.

[0139] FIG. 28 shows a flowchart 2800 outlining a procedure of sensing by proxy between an AP and three non-AP STAs (STA1, STA2, STA3) according to a third embodiment of the present disclosure. First, a basic SBP discovery is performed to discover the AP's support for SBP function. Then, STA1 may select the AP as its SBP responder. Then, STA1 may initiate an extended client discovery procedure to request the AP to provide a list of non-AP STAs (associated non-AP STAs and optionally non-associated non-AP STAs) and discover basic information of the AP and potential sensing responders.

[0140] STA1 discovers the AP through the client discovery procedure and selects it as the SBP responder. It then initiates the SBP procedure, requesting that the AP perform sensing measurements on its behalf by a specific target sensing responder (STA3 in this case) by sending a protected SBP request frame containing target device parameters such as location, coverage information, and the STA ID of the target sensing responder. Based on the target device parameters, the AP determines STA3 for sensing measurements and initiates sensing session setup and sensing measurement setup with the selected STA / link (STA3) by sending a protected sensing measurement setup request frame to STA3. The AP assigns a unique sensing measurement setup ID (MSID “1”) to the STA / link. The AP then sends a protected SBP response frame to indicate the successful setup with the sensing responders, the sensing responders’ link information, and their measurement setup IDs (“2”) back to STA1, completing the SBP setup.

[0141] After that, the AP performs sensing measurement with STA3 and sends an SBP report after collecting measurement reports on the link. In the report frame, the measurement setup ID ("1") of the link / STA is included to identify the measurement link.

[0142] STA1 then initiates a second SBP procedure, requesting that the AP perform sensing measurements on its behalf by another specific target sensing responder (STA2 in this case) by sending a protected SBP request frame containing target device parameters such as location, coverage information, and the STA ID of the target sensing responder. Based on the target device parameters, the AP determines STA2 for sensing measurements and initiates sensing session setup and sensing measurement setup with the selected STA / link (STA2) by sending a protected sensing measurement setup request frame to STA2. The AP assigns a unique sensing measurement setup ID (MSID “2”) to the STA / link. The AP then sends a protected SBP response frame to indicate the successful setup with the sensing responders, the sensing responders’ link information, and their measurement setup IDs (“2”) back to STA1, completing the SBP setup.

[0143] Then, the AP performs sensing measurement with STA2 and sends an SBP report after collecting measurement reports on the link. In the report frame, the measurement setup ID ("2") of the link / STA is included to identify the measurement link.

[0144] In this third embodiment, the selected sensing responder (e.g., STA2) may also need to verify whether the SBP initiator is authorized to obtain sensing measurement reports involving the selected sensing responder. Thus, during the sensing measurement setup phase after receiving an SBP request frame from the SBP initiator, the sensing measurement setup request frame sent to the sensing responder (e.g., STA2) includes the identity (e.g., MAC address) of the SBP initiator, so that the selected sensing responder can verify whether the SBP initiator is so authorized.

[0145] An exchange of additional authorization verification frames (e.g., frames requesting / including a password) may also be performed between the sensing responder and the SBP initiator (via the AP). If the authorization verification is successful, the sensing responder accepts the measurement setup request and the SBP setup is successful. If the authorization verification fails, the sensing responder rejects the measurement setup request and causes the SBP setup to fail.

[0146] FIG. 29 shows a flowchart 2900 illustrating a detailed procedure flow of a proxy sensing procedure between an AP that is an SBP responder and two non-AP STAs (STA1 that is an SBP initiator and STA2 that is a sensing responder) according to a third embodiment of the present disclosure. After a basic client discovery procedure and an extended client discovery procedure (not shown), STA1 initiates an SBP procedure and requests the AP to be a proxy sensing initiator on its behalf by sending a protected SBP request frame. Based on the target device parameters specified in the SBP request frame, the AP selects two STAs / links that are more relevant for sensing measurement (in this case, the AP-to-STA1 I2R link and the AP-STA2 I2R link that are associated with itself (STA1)).

[0147] The SBP initiator (STA1) may be associated with an AP (SBP responder), in which case it is assumed that the normal authentication / association procedures with the AP have already been completed and that a security association (SA) has already been set up, e.g., via a 4-way handshake, before the initiation of the SBP request. Alternatively, the SBP initiator (STA1) may not be associated with an AP, in which case it is assumed that the security associated with the AP has already been set up, e.g., through a pre-association security negotiation (PASN) via a 3-way handshake, before the initiation of the SBP request.

[0148] In this third embodiment, similar to the second embodiment, a unique Measurement Setup ID (MSID) is assigned to each measurement link. For example, the I2R link between the AP and STA1 is assigned MSID "1", and the link between the AP and STA2 is assigned MSID "2". Unlike the second embodiment, the SBP responder performs separate sensing procedures for different STAs / links.

[0149] 30 illustrates an exemplary format of a sensing measurement setup request frame 3000 according to a third embodiment of the present disclosure. The sensing measurement setup request frame 3000 includes a MAC header, a category field set to "public", a public action field set to "sensing measurement setup request", a dialogue token field, a re-setup bit field, a measurement setup ID field, a sensing measurement parameter element field, and an FCS field. The sensing measurement parameter element field has an element ID field, a length field, an element ID extension field, and a sensing measurement parameters field. The sensing measurement parameters field includes a sensing transmitter subfield, a sensing receiver subfield, a sensing measurement report subfield, a measurement report type subfield, an SBP procedure subfield, an SBP initiator ID present subfield, and an SBP initiator ID subfield. The SBP procedure subfield indicates that the sensing measurement setup request frame is for an SBP procedure, and the SBP initiator ID subfield indicates the ID of the SBP initiator. If the sensing initiator chooses to change attributes (parameters) of an existing sensing measurement setup, it sends the sensing measurement setup request frame 3000 with the re-setup bit field 3052 set to 1 to indicate that this is not a new sensing measurement setup request, but rather a request for a change in the sensing measurement setup parameters. If the re-setup bit field 3052 is equal to 1, the measurement setup ID field of the sensing measurement setup request frame indicates the measurement setup ID corresponding to the sensing measurement setup being re-setup.This use of re-setup of a sensing measurement setup request has the advantageous effect of changing the sensing measurement setup without the need to terminate the sensing measurement setup and perform a new sensing measurement setup.

[0150] Returning to FIG. 29, the SBP responder may first perform sensing setup with STA1, and then perform another sensing setup with STA2. In the case of sensing setup with STA2, upon receiving the sensing measurement setup request frame 3000, the sensing responder STA2 that received the request may perform authorization verification by sending a Protected Authorization Validation Request frame to the SBP initiator (STA1 in FIG. 29) via the SBP responder (AP in FIG. 29) to verify whether the SBP initiator (STA1) is authorized for the SBP procedure. Upon receiving the Protected Authorization Validation Request frame, the SBP initiator returns a Protected Authorization Validation Response frame including validation information (e.g., a shared password) in a requested format to the sensing responder via the SBP responder.

[0151] If the authorization verification is successful, the steps shown in block 2902 are executed, and if the authorization verification is unsuccessful, the steps shown in block 2904 are executed. In particular, if the authorization verification is successful, the sensing responder accepts the sensing measurement setup request and sends back a measurement setup response frame including its measurement setup ID "2" assigned by the SBP responder to the SBP responder to indicate that the SBP setup is successful. The SBP responder then sends a protected SBP response frame to the SBP initiator to indicate that the SBP setup with the STA / link under the measurement setup ID "2" is successful.

[0152] If the authorization verification fails, the sensing responder sends back a measurement setup response frame including its measurement setup ID "2" assigned by the SBP responder to the SBP responder to indicate that the SBP setup has failed. The SBP responder then sends a protected SBP response frame to the SBP initiator to indicate that the SBP setup with the STA / link has failed under measurement setup ID "2". However, even though the AP cannot perform sensing measurements for STA2 by proxy on behalf of STA1, it can still perform I2R measurements and reporting between STA1 and the AP.

[0153] In one embodiment, the AP may skip the authorization verification request / response if it has other means to verify whether the STA is authorized to obtain information about other STAs, for example, if the AP maintains a list of authorized devices or if the AP references the list of authorized devices from a database such as a server.

[0154] When STA1 receives the sensing measurement setup request frame 3000, STA1 accepts the sensing measurement setup without exchanging authorization verification frames, and replies to the SBP responder with a protected sensing measurement setup response frame including the measurement setup ID "1" assigned by the SBP responder for the SBP procedure, indicating that the SBP setup is successful. The SBP responder then sends a protected SBP response frame to the SBP initiator to indicate that the SBP setup with the STA / link under the measurement setup ID "1" is successful.

[0155] 31 illustrates an exemplary format of a protected authorization validation request frame 3100 according to a third embodiment of the present disclosure. The protected authorization validation request frame 3100 includes a MAC header (Frame Control, Duration, RA, and TA fields), a Category field set to “Protected Discovery”, an Action field set to “Protected Authorization Validation Request Frame”, a Dialog Token field, a Requesting STA ID field, a Target STA ID field, a Validation Mode field, and an FCS field.

[0156] FIG. 32 is an exemplary format of a protected authorization validation response frame 3200 according to a third embodiment of the present disclosure. The protected authorization validation response frame 3200 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected authorization validation response frame", a dialog token field, a requesting STA ID field, a target STA ID field, a validation mode field, a validation information field, and an FCS field. The requesting STA ID of the authorization validation frame 3100, 3200 indicates the ID (e.g., MAC address) of the STA requesting validation. The target ID of the authorization validation frame 3100, 3200 indicates the ID (e.g., MAC address) of the SBP initiator STA. The validation mode is set to 0 to indicate a plaintext password and 1 to indicate a hashed password. The validation information of the authorization validation response frame 3200 includes a PN / TSF field, a length subfield, and a validation text subfield. The PN / TSF field contains a packet number or a time synchronization function used as a salt to prevent replay attacks. The Length subfield indicates the length of the text in the Verification Text subfield. The Verification Text subfield contains either a plaintext password or a hashed password, based on the Verification Mode field.

[0157] For example, the hashed password is SHA-256(Key,PN / TSF||"plaintext password"), where "Key" is a common private secret key known to both parties, e.g., it may be a PTK generated during security association or a dedicated secret key for sensing provided by the AP / upper layer application, "||" is the concatenation operation, and "PN / TSF" is the value of the PN / TSF field, and the transmitter should ensure that it never uses the same value twice to prevent replay attacks. For example, it may be a monotonically increasing number or may contain the current value of the transmitter's time synchronization function (TSF).

[0158] According to a third embodiment of the present disclosure, FIG. 33A and FIG. 33B show an example format of an SBP response frame 3300 and a protected SBP response frame 3310, respectively. The SBP response frame 3300 includes a MAC header (frame control, duration, RA, and TA fields), a category field set to "public", a public action field set to "SBP response", a dialog token field, a status code field, a measurement setup ID field, an SBP parameter element field, and an FCS field. The protected SBP response frame 3310 includes a MAC header (frame control, duration, RA, and TA fields), a category field set to "protected public action dual", a public action field set to "protected SBP response", a dialog token field, a status code field, a measurement setup ID field, an SBP parameter element field, and an FCS field. The SBP parameter element fields may be similar to those described in FIG. 15.

[0159] In this third embodiment, the SBP initiator requests two separate SBP procedures, and therefore two SBP response frames are sent separately for different STAs / links. No additional link information fields are included in the SBP response frames, because the Measurement Setup ID field of each SBP response frame identifies the Measurement Setup ID value that corresponds to the sensing measurement link assigned by the SBP responder.

[0160] Also, in one implementation according to the third embodiment of the present disclosure, if the SBP initiator is one of the sensing responders (and sensing receivers), the measurement reports for the I2R or R2R links to which the SBP initiator is attached need not be sent to the SBP responder, and the SBP report need not include the measurement reports for such I2R or R2R links, since the SBP initiator already knows the results of the sensing measurements performed by the SBP initiator itself. This can be indicated by setting the "No Report for SBP Initiator Links" field in the SBP request frame.

[0161] 34 illustrates an example format of an SBP request frame 3400 according to a third embodiment of the present disclosure. The SBP request frame 3400 includes a MAC header (Frame Control, Duration, TA, and RA fields), a Category field set to "Public", a Public Action field set to "SBP Request", a Dialog Token field, an SBP Parameter Element field, and an FCS field. The SBP Parameter Element field includes an Element ID field, a Length field, an Element ID Extension field, and an SBP Parameters field. The SBP Parameters field includes a Target Device Parameters subfield, a Link Parameters subfield, a Measurement Parameters subfield, and a Report Parameters subfield, which specify attributes related to the target STA / link, the link being measured, the Measurement PPDU, and the SBP report, respectively.

[0162] In particular, the reporting parameters subfield includes a measurement report type subfield, a reporting frequency subfield, a channel state information (CSI) variation threshold subfield, and a no reporting for additional SBP initiator links subfield. If the no reporting for SBP initiator link subfield is set to 1, the SBP responder (AP) assigns the SBP initiator as a sensing receiver in any R2R or I2R links that include the SBP initiator and shall not solicit sensing measurement reports from the SBP initiator in such links. Also, the SBP responder shall not include measurement reports in SBP report frames in links with the SBP initiator.

[0163] Returning to Figure 29, in the SBP request frame, the no report subfield for the SBP initiator link in the SBP parameters field is set to 1, indicating that the SBP responder should not solicit sensing measurement reports from the SBP initiator for the link associated with the SBP initiator. Thus, during the measurement instance, upon receiving an I2R measurement PPDU (e.g., sensing NDP) from the AP, the SBP initiator STA1 does not send its own measurement report to the AP on the I2R link. The SBP responder also does not include a measurement report for the link associated with STA1 in the SBP initiator.

[0164] FIG. 35 illustrates an example configuration of a communication device 3500. The communication device 3500 is implemented as a STA for proxy sensing according to various embodiments of the present disclosure. The communication device may include at least one antenna 3522 for transmitting and receiving signals (for simplicity, only one antenna is shown in FIG. 35). The communication device 5200 also includes an 802.11 MAC / PHY sublayer 3504 with a sensing module 3506 for channel measurement, layer management service interfaces such as MLME SAP 3508 and MAC SAP 3510 where defined primitives are exchanged to communicate information and layer management functions such as WLAN sensing can be invoked, and higher layer applications (e.g., WLAN sensing abstraction layer 3514) communicating with the 802.11 MAC / PHY 3504 via the MLME SAP 3508.

[0165] Additionally, the 802.11 MAC / PHY sublayer 3504 may communicate with a WLAN data application (not shown) via the MAC SAP 5210. In this example, the sensing module 3506 performs channel measurements and provides raw results to the WLAN sensing abstraction layer 3514 via a WLAN sensing API. The WLAN sensing abstraction layer 3514 may collect and consolidate channel measurement results from 802.11 devices and process the results (e.g., smoothing compression, etc.) before passing the processed results to WLAN sensing client applications such as WLAN sensing client application 1 (vital signs detection) 3516 and WLAN sensing client application 2 (motion detection) 3516. The WLAN sensing client applications such as 3516, 3518 may perform WLAN sensing based on the channel measurements (e.g., using application-specific machine learning algorithms, etc.) and provide the results of the WLAN sensing, in this case the presence / absence of human detection and human motion detection.

[0166] The communication device further comprises a Station Management Entity (SME) (not shown), which is a layer dependent entity that performs functions on behalf of a general system management entity and implements standard management protocols to ensure correct MAC operation. The layer dependent entity provides interfaces such as MLME SAP 3508 and PLME SAP (not shown) for exchanging primitives and communication with the MLME and PLME respectively.

[0167] In one embodiment, the communication device may be an SBP initiator, and an upper layer application may issue an MLME primitive (not shown), for example using an MLME-SBP.request primitive, to initiate an SBP procedure.

[0168] The MAC / PHY sublayer 3504 may be configured to receive information or MAC / PHY parameters related to WLAN sensing to form an SBP request frame, and the trigger frame or PPDU is transmitted from the antenna 3522 via at least one wireless transmitter (not shown) to one or more communication devices (e.g., APs or SBP responders).

[0169] The MAC / PHY sublayer 3504 may also be configured to extract response PPDUs or measurement PPDUs, such as SBP response frames and SBP report frames received from another communication device, and pass information related to the received PPDUs to the sensing module 3506.

[0170] The sensing module 3506 further comprises a CSI feedback encoding / decoding module configured to decode and encode CSI information, e.g., information of CSI sub-components (e.g., amplitude, phase, I and Q) indicated by the report type indicator, in accordance with various above-described embodiments of the present disclosure.

[0171] FIG. 36 illustrates another exemplary configuration of a communication device 3600. The communication device 3600 is implemented as an AP or SBP responder for sensing by a proxy according to the present disclosure. The communication device 3600 includes a power supply 3602, a memory 3604, a CPU 3606 with at least one processor, a secondary storage device 3608, a wired I / F 3610, and a wireless I / F 3612. The memory 3604 may be a non-transitory computer-readable storage medium on which data representing instructions executable by at least one processor of the CPU 3606 to communicate with the wireless I / F 3612 to perform multi-generation random access according to various embodiments of the present disclosure is stored. The wireless IF 3612 includes a MAC layer 3614 and a PHY layer 3616. The PHY layer 3616 connects with a wireless transmitter (not shown), a wireless receiver (not shown), and an antenna 3622 used to transmit / receive signals to / from other (base) communication devices. Alternatively, the communication device 3600 may transmit / receive signals to / from other communication devices via the wired I / F 3610.

[0172] The MAC layer 3614 further comprises a link / STA selection module 3618, which stores information of the non-AP STAs 3620. The link / STA selection module 3618 may be configured to utilize information of the non-AP STAs 3520 to generate and process frames (e.g., SBP request / response frames, sensing measurement setup request / response frames, authorization verification request / response frames, measurement reports, SBP report frames), act as a proxy sensing initiator for the SBP initiator, and perform proxy sensing procedures for the SBP initiator, according to the various embodiments described above.

[0173] As described above, the embodiments of the present disclosure provide an improved communication system, communication method, and communication device for sensing with proxy procedure in MIMO WLAN networks.

[0174] The present disclosure can be implemented by software, hardware, or software cooperating with hardware. Each functional block used in the description of the above embodiment may be realized, in part or in whole, as an LSI, which is an integrated circuit, and each process described in the above embodiment may be controlled, in part or in whole, by one LSI or a combination of LSIs. The LSI may be formed individually as a chip, or one chip may be formed to include some or all of the functional blocks. The LSI may include a data input / output unit coupled to it. Depending on the degree of integration, the LSI may also be called an IC (integrated circuit), a system LSI, a super LSI, or an ultra LSI. However, the technology for implementing the integrated circuit is not limited to the LSI, and may be implemented by using a dedicated circuit, a general-purpose processor, or a dedicated processor. Furthermore, an FPGA (field programmable gate array) that can be programmed after the LSI is manufactured, or a reconfigurable processor that can reconfigure the connections and settings of the circuit cells arranged inside the LSI, may also be used. The present disclosure may be implemented as digital processing or analog processing. If, as a result of advances in semiconductor technology or other derivative technologies, LSI is replaced by a future integrated circuit technology, the future integrated circuit technology can be used to integrate the functional blocks. Biotechnology can also be applied.

[0175] The present disclosure may be implemented by any kind of apparatus, device or system having a communication capability (referred to as a communication apparatus).

[0176] Non-limiting examples of communication devices include telephones (e.g., cell phones, smartphones, etc.), tablets, personal computers (PCs) (e.g., laptops, desktops, notebooks, etc.), cameras (e.g., digital still cameras / camcorders), digital players (e.g., digital audio players / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, communication-enabled vehicles (e.g., cars, airplanes, boats, etc.), and combinations of the above devices.

[0177] Communications Equipment is not limited to portable or mobile, but also includes non-portable or fixed equipment, devices and systems of any kind, such as smart home devices (appliances, lighting, smart meters or metering devices, control panels, etc.), vending machines and any other "Things" that may be present on an Internet of Things (IoT) network.

[0178] Communications may include, for example, exchanging data through cellular systems, wireless LAN systems, satellite systems, etc., as well as various combinations thereof.

[0179] A communications unit may include devices such as a controller or a sensor coupled to the communications device to perform the communications functions described in this disclosure. For example, a communications unit may include a controller or a sensor that generates control or data signals used by the communications device to perform the communications functions of the communications unit.

[0180] The communications apparatus may further include infrastructure facilities, such as base stations, access points, and any other apparatus, devices, or systems that communicate with or control apparatuses such as the apparatuses in the non-limiting examples above.

[0181] Although some features of the various embodiments are described with reference to a device, it will be understood that the corresponding features also apply to the methods of the various embodiments, and vice versa.

[0182] Those skilled in the art will appreciate that numerous variations and / or modifications may be made to the present disclosure as illustrated in the specific embodiments without departing from the spirit or scope of the disclosure as broadly described, and therefore, the present embodiments are to be considered in all respects as illustrative and not restrictive.

Claims

1. a transmitter that, in operation, transmits a request frame to a second communication device, the request frame including a number of parameters used by the second communication device to perform measurements with one or more responder stations; a receiver that, during operation, receives from the second communication device a report frame including one or more sensing reports corresponding to the one or more responder stations; A first communication device comprising:

2. the plurality of parameters relate to at least one of link-related parameters, device-related parameters, a number of links to be selected, a condition for whether a responder-to-responder (R2R) link can be selected, and a condition for whether a link associated with the first communication device can be selected; The first communication device according to claim 1 .

3. The link-related parameter is at least one of a received signal strength indicator and a received channel power indicator received on a link, and the device-related parameter is at least one of a device type, a device location, a device identifier, and a device address. The first communication device according to claim 2 .

4. the report frame includes ID information for identifying each of the one or more responder stations. The first communication device according to claim 1 .

5. the receiving unit receives, before receiving the report frame, a response frame including the ID information for identifying each of the one or more responder stations from the second communication device; The first communication device according to claim 4 .

6. The request frame further indicates whether the one or more sensing reports included in the report frame include a report of a measurement related to a link to which the first communication device is attached. The first communication device according to claim 1 .

7. The receiver further receives, prior to receiving the report frame, a validation request frame requesting validation information indicating that the first communication device is authorized to receive the one or more sensing reports; the transmitting unit transmits a verification response frame including verification information generated based on the verification request frame. The first communication device according to claim 1 .

8. the request frame is a Sensing By Proxy (SBP) request frame, the response frame is an SBP response frame, and the measurement is a sensing measurement; The report frame is an SBP report frame. The first communication device according to claim 1 .

9. the first communication device and the one or more responder stations are non-access point (non-AP) stations, and the second communication device is an access point; The first communication device according to claim 1 .

10. a receiver that, in operation, receives from a first communication device a request frame including a number of parameters used by a second communication device to perform measurements with one or more responder stations; a circuit configured, in operation, to perform measurements with the one or more responder stations; a transmitter that, during operation, transmits a report frame to the first communication device, the report frame including one or more sensing reports corresponding to the one or more responder stations; A second communication device comprising:

11. the circuitry, in operation, selects the one or more responder stations based on the plurality of parameters. A second communication device according to claim 10.

12. the circuitry is configured to generate, prior to transmission of the report frame, a setup request frame for each of the one or more third communication devices to set up the measurements for each of the one or more responder stations, the setup request frame including an identifier or address of the first communication device; the transmitter transmits the setup request frame to each of the one or more third communication devices; A second communication device according to claim 10.

13. The receiver receives a validation request frame from one of the one or more responder stations, the validation request frame requesting validation information indicating that the first communication device is authorized to receive a measurement report from the one of the one or more responder stations, and the transmitter transmits the validation request frame to the first communication device; Then, the receiving unit further receives a verification response frame including the verification information from the first communication device; the transmitter transmits the validation response frame to the one of the one or more responder stations. A second communication device according to claim 10.

14. the validation request frame and the validation response frame include an identifier or address of each of the first communication device and the one or more third communication devices; A second communication device according to claim 13.

15. the report frame includes ID information for identifying each of the one or more responder stations. A second communication device according to claim 10.

16. the circuitry is configured to assign a different setup identifier to each of the one or more links and generate a response frame after receiving the request frame including the different setup identifier assigned to each of the one or more links; the information included in the report frame includes the different setup identifiers assigned to each of the one or more links. A second communication device according to claim 15.

17. the request frame is a Sensing By Proxy (SBP) request frame, the response frame is an SBP response frame, and the measurement is a sensing measurement; The report frame is an SBP report frame. A second communication device according to claim 10.

18. the first communication device and the one or more responder stations are non-access point (non-AP) stations, and the second communication device is an access point; A second communication device according to claim 10.

19. 1. A communication method implemented by a first communication device, comprising: transmitting a request frame to a second communication device, the request frame including a number of parameters used by the second communication device to perform measurements with one or more responder stations; receiving a report frame from the second communication device, the report frame including one or more sensing reports corresponding to the one or more responder stations; A communication method comprising:

20. A communication method implemented by a second communication device, comprising: receiving a request frame from a first communication device, the request frame including a number of parameters used by the second communication device to perform measurements with one or more responder stations; performing measurements with the one or more responder stations; transmitting a report frame to the first communication device, the report frame including one or more sensing reports corresponding to the one or more responder stations; A communication method comprising:

Images