Systems, apparatuses, and methods for providing wlan vendor specific awareness reports using coordinated transmissions between multiple access points

Abstract

There is provided a computerized method having the steps of: transmitting a signal for broadcasting a multi-report type support capability; receiving, from a device, a first request with an indication of the multi-report type support capability; sending a first response to the device with an acknowledgement of the multi-report type support capability; exchanging information for selecting a report type with the device; one or more perceptual measurement reports generated using the selected report type are received from the device.

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Patent Application No. 18 / 214,120, filed June 26, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0002] This invention generally relates to wireless systems, apparatuses, and methods, and more particularly to wireless systems, apparatuses, and methods for providing WLAN vendor-specific perception reports using coordinated transmissions between multiple access points. Background Technology

[0003] Wireless communication systems are known. For example, the IEEE 802.11 standard provides specifications for wireless local area networks (WLANs) to wirelessly connect multiple computing devices to form wireless computer networks in small areas (compared to "wide area networks") such as homes, schools, and buildings.

[0004] For example, IEEE 802.11bf is a task group within the IEEE 802.11 Wireless LAN project, whose work is to enable IEEE 802.11 devices to support an extended standard (revision) for WLAN awareness, which enables awareness of the following: • Targets, such as objects, humans, animals, etc.; • Various characteristics of the target, such as range (i.e., distance), speed, angle, movement, presence or proximity, gestures, etc.; • Environment, such as rooms, houses, vehicles, business or commercial environments, office / campus facilities, etc.

[0005] Therefore, next-generation wireless communication systems may include sensing technologies for a variety of uses and benefits. Summary of the Invention

[0006] According to one aspect of this disclosure, a computerized method is provided, comprising: transmitting a signal for broadcasting a multi-report type support capability; receiving from a device a first request indicating the multi-report type support capability; sending to the device a first response acknowledging the multi-report type support capability; exchanging with the device information for selecting a report type; and receiving from the device one or more perception measurement reports generated using the selected report type.

[0007] In some embodiments, the first request is a probe request defined based on the IEEE 802.11 standard, and the first response is a probe response defined based on the IEEE 802.11 standard.

[0008] In some embodiments, exchanging information with the device for selecting a report type includes: sending a request frame that includes one or more sense measurement report types; and receiving a response frame that includes a report type selected from one or more sense measurement report types.

[0009] In some embodiments, one or more perception measurement report types include a default perception measurement report type and at least one vendor-specific perception measurement report type.

[0010] In some embodiments, one or more perception measurement report types include at least one first perception measurement report type associated with a first identifier (ID), and a second perception measurement report type not associated with any ID.

[0011] In some embodiments, the request frame includes a first field, which includes a first predefined value indicating that the request frame includes one or more perception measurement report types.

[0012] In some embodiments, the request frame is a sensing measurement establishment request frame defined based on the IEEE 802.11 standard, and the response frame is a sensing measurement establishment response frame defined based on the IEEE 802.11 standard; the first field is a sensing measurement parameter field defined based on the IEEE 802.11 standard; and the first predefined value is the value of the sensing measurement report type subfield of the sensing measurement parameter field.

[0013] In some embodiments, the first predefined value is 7.

[0014] In some embodiments, the request frame includes a second field, which includes one or more perception measurement report types.

[0015] In some embodiments, the second field further includes: a second ID having a second predefined value; a length subfield for indicating the length of the second field; and a third ID.

[0016] In some embodiments, the third ID is an organizationally unique identifier (OUI).

[0017] In some embodiments, the second predefined value is 221.

[0018] In some embodiments, the second field further includes one or more subfields, each of the one or more subfields including: a fourth ID; a length item for indicating the length of the subfield; a perception measurement report type item; and perception measurement parameters.

[0019] In some embodiments, the first field may also include a count of the number of one or more subfields of the second field.

[0020] In some embodiments, if one or more perception measurement report types include multiple perception measurement report types, the first predefined value is 6; or if one or more perception measurement report types include only a single perception measurement report type, the first predefined value is 7.

[0021] In some embodiments, the response frame includes a third field, which includes a third predefined value indicating whether the selected report type is included in the response frame.

[0022] In some embodiments, one or more sensing measurement report types include a channel state information (CSI) quantization report, which is generated by the device using a process including the following steps: acquiring a channel estimate; normalizing the phase of the channel estimate by π; quantizing the normalized phase; normalizing the amplitude of the channel estimate by the maximum amplitude value; and quantizing the normalized amplitude.

[0023] According to one aspect of the present invention, a module is provided, comprising one or more circuits for performing the above-described method.

[0024] According to one aspect of the invention, one or more non-transitory computer-readable storage media are provided, comprising computer-executable instructions, wherein the instructions, when executed, cause at least one processing unit to perform the method described above.

[0025] The methods, modules, and / or one or more non-transitory computer-readable storage media described above provide various benefits, such as: • The above method allows sensing stations (STAs) to negotiate vendor-specific sensing measurement report types with peer sensing stations (such as other STAs and / or APs), thereby providing flexibility for sensing reporting.

[0026] • The above request and response frames allow sensing nodes (such as sensing STAs and sensing APs) to easily exchange vendor-specific sensing measurement reports.

[0027] • The above request and response frames allow sensing nodes to exchange a list of sensing measurement reports, including IEEE 802.11bf defaults and vendor-specific reports.

[0028] • The DMG perception measurement setup element and DMG perception report element allow perception nodes to negotiate vendor-specific DMG perception measurement report types.

[0029] • CSI quantification reports facilitated negotiation as a vendor-specific option. Attached Figure Description

[0030] Figure 1 These are simplified schematic diagrams illustrating a communication system according to some embodiments of the present invention; Figure 2 yes Figure 1 A simplified diagram of the access point (AP) of the communication network of the communication system shown in the figure; Figure 3 yes Figure 1 A simplified diagram of a communication system station (STA) is shown. Figure 4 It is shown Figure 1 The diagram shows a simplified schematic of a wireless communication system that provides wireless communication signals for home coverage. Figure 5 It shows the use Figure 1 The diagram shows a wireless communication system using wireless communication signals to detect intruders. Figure 6 It shows the use Figure 1 The diagram shows a wireless communication system using wireless communication signals for fall detection. Figure 7A and Figure 7B It shows the use Figure 1 The diagram shows a wireless communication system using wireless communication signals for gesture recognition. Figure 8 It shows the use Figure 1 A simplified schematic diagram illustrating the layout analysis of wireless communication signals in a wireless communication system. Figure 9 It shows the use Figure 1 The diagram illustrates an example of two sensing communication nodes sensing a target in a wireless communication system. Figure 10 This is a flowchart illustrating the sensing process as specified by IEEE 802.11bf; Figure 11A This is a message flow diagram according to some embodiments of the present invention, illustrating in Figure 9 An exemplary message flow of the perception session report negotiation method for establishing a related perception session between the perception initiator and the perception responder is shown; Figure 11B This is a message flow diagram according to some embodiments of the present invention, illustrating in Figure 9 An exemplary message flow of a perception session report negotiation method for establishing a non-associated perception session between a perception initiator and a perception responder is shown; Figure 12 This is illustrated in some embodiments according to the present invention. Figure 11A and / or Figure 11B The message flow diagram shown is a schematic diagram of the structure of the perception measurement-based request frame used in the message flow diagram. Figure 13 According to some embodiments of the present invention Figure 12 The diagram shows the structure of the perception measurement parameter field in the perception measurement establishment request frame. Figure 14 According to some embodiments of the present invention Figure 12 The diagram shows the structure of the vendor-specific report sub-element field in the perception measurement establishment request frame; Figure 15 This is illustrated in some embodiments according to the present invention. Figure 11A and / or Figure 11B The diagram shown illustrates the structure of the response frame established by the sensing measurements used in the message flow graph. Figure 16 This is illustrated in some embodiments according to the present invention. Figure 11A and / or Figure 11B The message flow diagram shown is a schematic diagram of the structure of the perception measurement-based request frame used in the message flow diagram. Figure 17 According to some embodiments of the present invention Figure 16 The diagram shows the structure of the report type list field in the perception measurement establishment request frame; Figure 18 This is an illustration of some embodiments of the present invention. Figure 17 The diagram shows the structure of the report type subfield in the report type list field. Figure 19 According to some embodiments of the present invention Figure 16 The diagram shows the structure of the perception measurement parameter field in the perception measurement establishment request frame. Figure 20 This is a schematic diagram illustrating the structure of a directional multi-gigabit (DMG) sensing measurement establishment element according to some embodiments of the present invention; Figure 21 This is a schematic diagram of the structure of a DMG sensing reporting element according to some embodiments of the present invention; and Figure 22 This is an illustration of some embodiments of the present invention. Figure 9 The flowchart shown illustrates an exemplary CSI quantization process performed by a sensing responder to generate a CSI quantization report. Detailed Implementation

[0031] The embodiments disclosed herein relate to wireless systems, apparatuses, and methods for providing WLAN vendor-specific perception reports using coordinated transmissions between multiple access points. In this document, the term "vendor-specific perception report" or "vendor-specific perception measurement report" refers to a perception measurement report customized by the vendor or provider of the wireless system, apparatus, method, and / or a non-transitory computer-readable storage medium, which includes computer-executable instructions for implementing these methods. Therefore, the term "vendor-specific report type" or "vendor-specific perception measurement report type" refers to a perception measurement report type customized by the vendor or provider. In a broader sense, a vendor's vendor-specific perception measurement report and vendor-specific perception measurement report type are associated with the vendor's unique identifier (ID), such as the vendor's Organizational Unique Identifier (OUI; assigned by the IEEE Registry; see https: / / standards.ieee.org / products-programs / regauth / oui / ).

[0032] The wireless systems, apparatuses, and methods disclosed herein can be any suitable system, apparatus, and method for transmitting wireless signals. An example of such systems could be Wi-Fi. ® The system (WI-FI is a registered trademark of the Wi-Fi Alliance in Austin, Texas, USA). Other examples of these systems could be 5G, 6G, or other applicable future wireless mobile communication systems, etc.

[0033] A. System Structure Now go to Figure 1 The accompanying drawings illustrate communication systems according to some embodiments of the present invention, and are generally identified by reference numeral 100. For example, the communication system 100 in these embodiments may be a Wi-Fi system built under relevant standards such as the IEEE 802.11 standard. ® The system, as shown, includes one or more interconnected network devices 102 forming a distribution system (DS) 104, such as one or more interconnected access points (APs; also called "base stations"). The DS 104 is connected in turn to other networks such as the Internet 106, which may include computer networks and subnets (internal networks) or both, and includes protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP).

[0034] Each AP 102 wirelessly communicates with one or more mobile or fixed stations (STAs) 112 via a corresponding wireless channel 114, using wireless signals transmitted between them (also identified as 114), to provide a wireless network connected to them. In this document, AP 102 and STA 112 can be considered as different types of network nodes (also referred to as "communication nodes" or simply "nodes") of the communication system 100. Each AP 102 and the STAs 112 connected to it form a cell or basic service set (BSS) 118.

[0035] Figure 2 This is a simplified schematic diagram of AP 102. As shown, AP 102 includes at least one processing unit 142, at least one transmitter (Tx) 144, at least one receiver (Rx) 146 (collectively referred to as transceivers), one or more antennas 148, at least one memory 150, and one or more input / output components or interfaces 152. A scheduler 154 may be coupled to the processing unit 142. The scheduler 154 may be included within AP 102 or operate separately from AP 102.

[0036] Processing unit 142 is a circuit for performing various processing operations, such as signal encoding, data processing, power control, input / output processing, or any other suitable function. Processing unit 142 may include a microprocessor, microcontroller, digital signal processor, FPGA, ASIC, etc. In some embodiments, processing unit 142 may execute computer-executable instructions or code stored in memory 150 to perform the various processes (also referred to as methods) described below.

[0037] Each transmitter 144 may include any suitable structure for generating signals, such as control signals described in detail below, for wireless transmission to one or more STAs 112. Each receiver 146 may include any suitable structure for processing signals wirelessly received from one or more STAs 112. Although shown as separate components, at least one transmitter 144 and at least one receiver 146 may be integrated and implemented as a transceiver. Each antenna 148 may include any suitable structure for transmitting and / or receiving wireless signals. Although in Figure 2 The diagram shows a common antenna 148 coupled to both transmitter 144 and receiver 146, but one or more antennas 148 may be coupled to transmitter 144, and one or more other antennas 148 may be coupled to receiver 146.

[0038] In some embodiments, AP 102 may include multiple transmitters 144 and receivers 146 (or multiple transceivers) and multiple antennas 148 for communication within its cell 118 using, for example, multiple-input multiple-output (MIMO) technology and / or multi-link operation (MLO). Furthermore, orthogonal frequency-division multiplexing (OFDM) may be used, where channel 114 is divided into multiple orthogonal sub-channels for communication between AP 102 and STA 112.

[0039] Each memory 150 may include one or more non-transitory computer-readable volatile and / or non-volatile storage media, such as RAM, ROM, hard disk, optical disk, SIM card, solid-state memory, memory stick, SD memory card, etc. Memory 150 may be used to store instructions executable by processing unit 142, and data used, generated, or collected by processing unit 142. For example, memory 150 may store instructions for software, software systems, or software modules executable by processing unit 142, for implementing embodiments of some or all of the functions and / or processes performed by AP 102 as described herein.

[0040] Each input / output component 152 enables interaction with a user or other device in the communication system 100. Each input / output device 152 may include any suitable structure for providing or receiving information from the user, and may be, for example, a speaker, microphone, keypad, keyboard, display, touchscreen, network communication interface, etc.

[0041] In this document, STA 112 can be any suitable wireless device that can join communication system 100 via AP 102 for wireless operation. In various embodiments, STA 112 can be a wireless electronic device used by a human or user (e.g., a smartphone, mobile phone, personal digital assistant (PDA), laptop, desktop computer, tablet, smartwatch, consumer electronics, etc.). Alternatively, STA 112 can be a wireless sensor, Internet of Things (IoT) device, robot, shopping cart, vehicle, smart TV, smart home appliance, wireless transmit / receive unit (WTRU), mobile station, etc. Depending on the implementation, STA 112 can move autonomously or under direct or remote human control, or it can be located in a fixed position.

[0042] In some embodiments, STA 112 may be a multi-mode wireless electronic device capable of operating according to a variety of wireless access technologies and includes a plurality of transceivers necessary to support these technologies.

[0043] In addition, some or all of STA 112 include functions for communicating with different wireless devices and / or wireless networks via different wireless links using different wireless technologies and / or protocols. Instead of wireless communication (or other than wireless communication), STA 112 can communicate with other devices or switches (not shown) and the Internet 106 via wired communication channels. For example, multiple STA 112 (e.g., STA 112 in close proximity to each other) can communicate directly with each other via suitable wired or wireless sidelinks.

[0044] Figure 3 This is a simplified schematic diagram of STA 112. As shown, STA 112 includes at least one processing unit 202, at least one transceiver 204, at least one antenna or network interface controller (NIC) 206, at least one positioning module 208, one or more input / output components 210, at least one memory 212, and at least one other communication component 214.

[0045] Processing unit 202 is a circuit used to perform various processing operations, such as signal encoding, data processing, power control, input / output processing, or any other function, to enable STA 112 to access and join communication system 100 and operate therein. Processing unit 202 can also be used to implement some or all of the functions of STA 112 described in this invention. Processing unit 202 may include a central processing unit (CPU), microprocessor, microcontroller, digital signal processor, accelerator, graphics processing unit (GPU), tensor processing unit (TPU), FPGA, or ASIC. Examples of processing unit 202 may be: ARM processors from manufacturers such as Qualcomm in San Diego, California, USA. ® ARM architecture ® Microprocessor (ARM is a registered trademark of Arm, a company based in Cambridge, England); Intel ® Microprocessor (INTEL is a registered trademark of Intel Corporation, Santa Clara, California, USA); AMD ®Microprocessor (AMD is a registered trademark of Advanced Micro Devices, Inc., Sunnyvale, California, USA); etc. In some embodiments, processing unit 202 may execute computer-executable instructions or code stored in memory 212 to perform the various processes described below.

[0046] At least one transceiver 204 may be used to modulate data or other content for transmission by at least one antenna 206 to communicate with AP 102. The transceiver 204 is also used to demodulate data or other content received by the at least one antenna 206. Each transceiver 204 may include any suitable structure for generating signals for wireless transmission and / or for processing signals for wireless reception. Each antenna 206 may include any suitable structure for transmitting and / or receiving wireless signals. Although the transceiver 204 is shown as a single functional unit, it may be implemented independently as at least one transmitter and at least one receiver.

[0047] Positioning module 208 is used to communicate with multiple global or regional positioning devices (e.g., navigation satellites) to determine the location of STA 112. Navigation satellites may be satellites of a global navigation satellite system (GNSS), such as the US Global Positioning System (GPS), Russia's GLONASS, the European Union's Galileo positioning system, and / or China's BeiDou system. Navigation satellites may also be satellites of regional navigation satellite systems (RNSS), such as India's Indian Regional Navigation Satellite System (IRNSS) or Japan's Quasi-Zenith Satellite System (QZSS). In some other embodiments, positioning module 208 may be used to communicate with multiple indoor positioning devices to determine the location of STA 112.

[0048] One or more input / output components 210 are used to interact with a user or other device in the communication system 100. Each input / output component 210 may include any suitable structure for providing information to or receiving information from the user, and may be, for example, a speaker, microphone, keypad, keyboard, display, touch screen, etc.

[0049] At least one memory 212 is used to store instructions executable by the processing unit 202 and data used, generated, or collected by the processing unit 202. For example, the memory 212 may store instructions for software, software systems, or software modules executable by the processing unit 202 to implement some or all of the functions and / or embodiments of the STA 112 described herein. Each memory 212 may include one or more non-transitory computer-readable volatile and / or non-volatile storage media and retrieval components, such as RAM, ROM, hard disk, optical disk, SIM card, solid-state storage module, memory stick, SD memory card, etc.

[0050] At least one other communication component 214 is used for communication via, for example, a radio link, BLUETOOTH ® Other communication methods, such as wired links (Bluetooth Sig Inc., Kirkland, Washington, USA), can be used to communicate with other devices like the STA 112. Examples of wired links include USB cables, network cables, parallel cables, and serial cables.

[0051] In some embodiments, STA 112 may include multiple transceivers 204 and multiple antennas 206 for communicating with AP 102 using technologies such as MIMO or MLO. STA 112 may also communicate with AP 102 using OFDM.

[0052] In the following text, AP 102 and STA 112 are generally classified as initiator and responder, respectively, where AP 102 can be an initiator when transmitting wireless signals or a responder when receiving wireless signals. Similarly, STA 112 can be an initiator when transmitting wireless signals or a responder when receiving wireless signals. In some embodiments, the two STAs 112 can operate as an initiator and a responder, respectively. Alternatively, the two APs 102 can operate as an initiator and a responder, respectively.

[0053] As those skilled in the art will understand, the channel 114 between AP 102 and STA 112 typically includes one or more Tx-Rx links (also referred to as "Tx-Rx link pairs"), each link corresponding to a pair of Tx and Rx. Depending on the communication direction, the Tx and Rx may be located on the AP side and the STA side, or on the STA side and the AP side, respectively.

[0054] Channel 114 can be estimated by sending a set of predefined symbols (as a reference signal (RS)) from the initiator (which could be AP 102 or STA 112) to the responder (correspondingly, STA 112 or AP 102). The responder uses the received symbols and the predefined symbols to estimate the parameters of channel 114 and feeds back the estimated channel parameters as channel station information (CSI) to the initiator. In the 802.11 standard, channel state information (CSI) is also used to support beamforming.

[0055] B. Target perception In some embodiments of this disclosure, the communication system 100 or its sensing-capable communication nodes (e.g., sensing-capable AP 102 and / or sensing-capable STA 112) can use wireless communication signals 114 to sense targets and / or understand the environment to achieve various purposes. In this subsection, for ease of description, the sensing-capable communication node, the sensing-capable AP 102, and the sensing-capable STA 112 may be referred to as a "sensing node" (or simply "node"), a "sensing AP" (or simply "AP"), and a "sensing STA" (or simply "STA"), respectively.

[0056] In this section, various embodiments of the IEEE 802.11 standard (e.g., IEEE 802.11bf) are described. Detailed information on IEEE 802.11bf can be found in: "IEEE P802.11bf™ / D0.4, Draft Standard for Information technology – Telecommunications and information exchange between systems Local and metropolitan area networks – Specific requirements", published by IEEE in November 2022; "Threshold Based Sensing Measurement", published in IEEE 802.11-21 / 0351r5 on May 10, 2021, available at https: / / mentor.ieee.org / 802.11 / dcn / 21 / 11-21-0351-05-00bf-threshold-based-sensing-measurement.pptx; and "Proposed Draft Text for D0.1: Threshold-based Sensing", published in IEEE 802.11-22 / 0134r4 on February 24, 2022. The “Procedure” can be found at https: / / mentor.ieee.org / 802.11 / dcn / 22 / 11-22-0134-02-00bf-pdt-threshold-based-sensing-procedure.docx; the contents of this document are incorporated herein by reference in full.

[0057] Figures 4 to 8 Some examples of perception are shown. For example... Figure 4 As shown, the communication system 100 can provide a wireless communication signal 114 covering the home 242. For example... Figures 5 to 8 As shown, one or more sensing STAs 112 (not shown) can use wireless communication signal 114 to perform intruder detection (e.g., for detecting intruders; see [link]). Figure 5 ), used for fall detection (e.g., for detecting a person's fall; see Figure 6 ), used for gesture recognition (e.g., for recognizing gestures performed by a person; see Figure 7A and Figure 7B), or for layout analysis (e.g., using wireless communication signals 114 transmitted between AP 102 and multiple STA 112 to analyze the layout of home 242; see Figure 8 ).

[0058] Figure 9 This is a schematic diagram illustrating an example of a sensing target 306. As shown, a sensing initiator 302 (which is a Tx node adapted or otherwise capable of transmitting a wireless communication signal 114 for sensing) transmits a wireless communication signal 114, which includes, for example, protocol packet data units (PPDUs) for sensing measurements. A sensing responder 304 (which is an Rx node adapted or otherwise capable of receiving the wireless communication signal 114 and performing measurements for sensing) receives the wireless communication signal 114 (or more specifically, the PPDU) and its echo 308 reflected from a nearby target 306. The sensing responder 304 can detect and measure the received wireless communication signal 114 and / or the echo 308 and report the parameters it measures to the sensing initiator 302. Alternatively, the sensing responder 304 may detect and measure the received wireless communication signal 114 and / or echo 308, and may further measure parameters of the target 306 (e.g., azimuth, size, velocity, etc.) based on the received wireless communication signal 114 and / or its echo 308, and then report the detected target 306 and its parameters to the sensing initiator 302. Hereinafter, the term "measured value" or "measurement result" is used, which generally refers to the measured parameters of the received wireless communication signal 114, one or more measured parameters of the echo 308, and / or one or more measured parameters of the target 306. In some embodiments, multiple echoes 308 may be received.

[0059] Figure 10 This is a flowchart illustrating the sensing process 340 (also known as the "sensing protocol") as defined by IEEE 802.11bf. As shown, the sensing process 340 includes multiple phases. More specifically, after the start of process 340 (step 342), the sensing process 340 enters a sensing-discovery phase 344 for discovering sensing nodes (e.g., sensing initiator 302 and sensing responder 304) by exchanging information about sensing capabilities among the various communication nodes. In some embodiments, initiator 302 and responder 304 may associate with each other after the discovery phase.

[0060] Following perception discovery 344, a perception session 360 begins, in which the perception process 340 enters a perception establishment phase 346 to establish or otherwise initialize the perception session. During this phase, a threshold parameter can be sent from the initiator to the responder in a perception request frame. This threshold allows the receiver to determine when a change in the receiver's CSI indicates that an object has been detected.

[0061] Then, the sensing initiator 302 begins transmitting wireless communication signals 114. For example, the sensing initiator 302 can transmit a series of... m A null data packet (NDP) frame (as part of a PPDU frame). Sensing responder 304 receives the NDP frame and / or its echo from wireless communication signal 114, such as... Figure 9 As shown.

[0062] In the perception measurement phase 348, the perception responder 304 calculates the CSI for each NDP frame and performs measurements, for example: • CSI amplitude for each symbol per frame; • CSI phase for each symbol per frame.

[0063] In some embodiments, the CSI amplitude and phase are determined for each NDP frame.

[0064] During the perception reporting phase 350, the perception responder 304 feeds back the measurement results to the perception initiator 302. For example, the perception responder 304 can construct a perception report based on the CSI feedback and send the perception report to the perception initiator 302.

[0065] Then, the sensory session is terminated explicitly or implicitly 360 (termination phase 352).

[0066] The perception session 360 (including stages 344 to 352) can be repeated as needed. Once all perception sessions 360 are completed, the perception process 340 ends (step 354).

[0067] In target perception using wireless communication signal 114, communication system 100 needs to address several issues and / or design considerations.

[0068] For example, the received wireless communication signal 114 and / or its echo 308 may be affected by the wireless communication channel. Therefore, CSI can serve as input for sensing. In some use cases, CSI may vary over time, so for use cases such as intruder detection, sensing may require regular CSI feedback. CSI feedback over a period of time may be highly relevant.

[0069] Furthermore, some wireless communication standards, such as IEEE 802.11bf, allow devices like the AP 102 and / or STA 112 to implement sensing technologies in various frequency bands, including the 2.4 GHz, 5 GHz, and 6 GHz bands (collectively referred to as sub 7 GHz), and the 60 GHz millimeter wave band (also known as directional multi-gigabit (DMG)). Due to the historical work of IEEE 802.11, separate frame types have been defined for sub 7 GHz and DMG CSI measurements.

[0070] Some standards (such as IEEE 802.11) allow vendor-specific protocol elements, so vendors can build extensions on the IEEE 802.11 standard without modifying the IEEE 802.11 standard.

[0071] In IEEE 802.11i, the authentication and key management (AKM) mechanism includes an OUI to allow AKM to be defined outside of the IEEE 802.11 standard. The OUI is always included in the AKM announcement.

[0072] The AKM defined in the IEEE 802.11 standard uses the OUI assigned to the IEEE 802.11 working group (00-0F-AC). Other organizations (such as the Wi-Fi Alliance) provide Wi-Fi... ® Protected Access (WI-FI) ® protected access, WPA) (00-50-F2) and WI-FI ® The Easy Connect Network Introduction (50-6F-9A) defines AKM. The use of OUI in certain protocol elements of the IEEE 802.11 standard allows other organizations (not necessarily vendors) to provide standardization without modifying the IEEE 802.11 standard itself.

[0073] However, in some cases, the standardized sensing reports defined in IEEE 802.11bf may not be suitable for sensing applications. Vendors or other standards organizations may need to define alternative reports to address specific sensing applications.

[0074] Whenever a new perception reporting method is defined, the current IEEE 802.11bf amendments may have to be updated. Currently, there is only one CSI report defined in 802.11bf for sub 7 GHz perception and one CSI report defined for DMG perception, but DMG also defines six (6) other (non-CSI) report types.

[0075] In view of the above-mentioned problems and / or design considerations, in some embodiments, the communication system 100 provides a mechanism to support additional reporting methods and allows the sensing initiator 302 and sensing responder 304 to negotiate a reporting method as part of sensing measurement establishment 346. This mechanism involves modifications to sensing discovery 344, sensing establishment 346, sensing measurement 348, and / or sensing reporting 350 to allow sensing nodes to negotiate alternative reporting mechanisms.

[0076] More specifically, the communication system 100 announces or otherwise broadcasts various sensing measurement report types to all sensing nodes, such as default or standardized sensing measurement report types and vendor-specific sensing measurement report types that can be used by the sensing nodes. During the sensing establishment phase 346, the initiator 302 and the responder 304 negotiate the sensing report type used to report sensing measurements. During the sensing reporting phase 350, the responder 304 can send the report type along with necessary parameters and results.

[0077] Figure 11A This is a message flow diagram illustrating an exemplary message flow 400 of a method for negotiating a perception session report to establish an associated perception session between a perception initiator 302 (e.g., AP 102) and a perception responder 304 (e.g., STA 112). Those skilled in the art will understand that... Figure 11A The diagram shown is merely an example of a message sequence. In other embodiments, messages may be sent in a different order.

[0078] In step 402, AP 102 announces or otherwise broadcasts its multi-reporting capability (also referred to as "multi-reporting type support capability," i.e., the capability to support multiple sensing measurement report types) 344 by sending a short sensing capability element via a beacon to one or more STAs (e.g., STA 112 for sensing discovery). In these embodiments, AP 102 supports multiple vendor-specific sensing measurement report types. Therefore, AP 102 includes an indication (multi-reporting) in the short sensing capability element to indicate that it has multi-reporting type support capability, thereby supporting alternative (e.g., vendor-specific) reporting methods in addition to the default reporting type (e.g., CSI report).

[0079] STA 112 receives the beacon and discovers AP 102. STA 112 then sends a probe request (step 404), wherein the probe request includes a short sensing capability element with an indication (multi-reporting) to indicate that it has multi-reporting type support capability (i.e., supports multiple reporting types (but not necessarily the same reporting types as AP 102), and may include alternative reporting methods or types). AP 102 then responds to STA 112 with a probe response having a multi-reporting indication (step 406). After step 406, AP 102 and STA 112 are discovered by each other.

[0080] Before establishing a sensing session, STA 112 then determines whether to establish a non-associative sensing session or an associated sensing session. As those skilled in the art will understand, a non-associative sensing session may involve an insecure communication link between them, and / or such an insecure communication link may only be used for reporting sensing measurements. On the other hand, an associated sensing session establishes a security association (SA) between STA 112 and AP 102, which involves a secure communication link between the two, and / or the secure communication link can be used for reporting sensing measurements and network connectivity (i.e., for reporting both sensing measurements and conventional wireless data communication).

[0081] like Figure 11A As shown, STA 112 determines to establish an association sensing session. Therefore, in step 408, STA 112 sends an association request (with a short sensing capability element that has an indication (multiple reports) to indicate that it supports multiple reporting types) to AP 102 to request association. In response, AP 102 sends an association response (with a short sensing capability element that has an indication (multiple reports) to indicate that it supports multiple reporting types) to STA 112 to establish a secure communication link between AP 102 and STA 112 for reporting sensing measurements and for network connectivity (step 410).

[0082] In step 412, AP 102 sends a Sensing Measurement Establishment Request Frame to STA 112 for negotiating the Sensing Measurement Report Type. The Sensing Measurement Establishment Request Frame includes a list of report types supported by AP 102. The report list may include default report types and alternative report types.

[0083] STA 112 receives a sensing measurement setup request frame, selects a report type from the report type list received from AP 102, and sends a sensing measurement setup response frame with parameters (Selected-report-type) to AP 102 to notify AP 102 of the selected report type. The sensing session report negotiation between AP 102 and STA 112 is then completed. STA 112 then uses wireless communication signal 114 to sense one or more targets, generates one or more sensing measurement reports using the selected report type, and sends one or more sensing measurement reports to AP 102 (step 414).

[0084] In some embodiments, in step 412, AP 102 may include a single report type in the perception measurement setup request frame. The requested report type may be a default report type or a vendor-specific report type identified by the OUI. After receiving the perception measurement setup request frame, STA 112 may accept the report type and initiate a perception session, or it may reject the report type (e.g., if STA 112 does not support the report type). In some embodiments, in step 412, AP 102 may include multiple report types in the perception measurement setup request frame, and STA 112 may respond using one or more report types in perception measurement setup response step 414 to inform AP 102 of the report types it can use.

[0085] Figure 11B This is a message flow diagram illustrating an exemplary message flow 400 of a method for negotiating a perception session report to establish a non-associated perception session between a perception initiator 302 (e.g., AP 102) and a perception responder 304 (e.g., STA 112). Those skilled in the art will understand that... Figure 11B The diagram shown is merely an example of a message sequence. In other embodiments, messages may be sent in a different order.

[0086] Figure 11B The message flow 400 shown for establishing a non-associative awareness session is similar to Figure 11A The message stream shown is used to establish a correlation-aware session, but the difference is that... Figure 11B The message flow 400 shown does not include steps 408 and 410. Instead, Figure 11B The message flow 400 shown includes step 422, which is executed after step 406, wherein STA 112 sends a sensing measurement setup query (with an indication (multiple reports) to indicate that it supports multiple reporting types). AP 102 responds to the query with a sensing measurement setup request (step 412) as described above.

[0087] The method for negotiating perception session reports between AP 102 and STA 112 allows the perception STA 112 to negotiate vendor-specific perception measurement report types with peer perception sites (such as other STA 112 and / or perception AP 102), thereby providing flexibility for perception reporting.

[0088] Furthermore, in the above embodiment, AP 102 provides a list of sensing measurement report types in step 412 for STA 112 to select (step 414). Therefore, AP 102 can provide compatibility with various vendor-specific report types and makes it unnecessary for STA 112 to be responsible for providing such compatibility, thereby facilitating the design of compact and / or lightweight STA 112 (e.g., IoT devices).

[0089] Those skilled in the art will understand that in some other embodiments, STA 112 may perform step 412 to provide a list of sensing measurement report types for AP 102 to select (by performing step 414).

[0090] As described above, sensing measurement setup involves a sensing measurement setup request frame and a sensing measurement setup response frame (collectively, "sensing measurement setup frames"). In some embodiments, the two sensing measurement setup frames may include vendor-specific reporting information.

[0091] For example, Figure 12 This is a schematic diagram of the structure of a sensing measurement setup request frame 440 according to some embodiments of the present invention. In this example, the sensing measurement setup request frame 440 conforms to and is modified according to IEEE 802.11bf clause 9.6.7.49.

[0092] As shown, the Sensing Measurement Setup Request Frame 440 includes: a Category field 442 (one (1) octet or eight (8) bits); a Common Action field 444 (one (1) octet); a Dialogue Token field 446 (one (1) octet); a Measurement Setup ID field 448 (three (3) octets); a Sensing Measurement Parameter field 450 (variable size); and a Vendor-Specific Report Sub-Element field 452 (variable size) for specifying one or more vendor-specific report types (described in more detail later). The Category field 442, Common Action field 444, Dialogue Token field 446, and Measurement Setup ID field 448 are the same as those defined in IEEE 802.11-2020 and IEEE 802.11bf. The Sensing Measurement Parameter field 450 is similar to the field defined in IEEE 802.11bf, but has new values ​​for indicating the inclusion of vendor-specific report types.

[0093] Figure 13This is a schematic diagram illustrating the structure of the sensing measurement parameter field 450 in a sensing measurement setup request frame 440 according to some embodiments of the present invention. In this example, the sensing measurement parameter field 450 conforms to IEEE 802.11bf. Figure 9-10 02ax was modified.

[0094] like Figure 13 As shown, the sensing measurement parameter field 450 includes a sensing transmitter subfield 462 (one (1) bit), a sensing receiver subfield 464 (one (1) bit), a sensing measurement report request subfield 466 (one (1) bit), a sensing measurement report type subfield 468 (three (3) bits), and a measurement setup expiration index subfield 470 (four (4) bits). The sensing measurement parameter field 450 may also include other subfields (in Figure 13 The terminology used is TBD (To Be Determined) 472. The Sensing Transmitter subfield 462, Sensing Receiver subfield 464, Sensing Measurement Report Request subfield 466, and Measurement Setup Expiry Date subfield 470 are identical to those defined in IEEE 802.11bf. The Sensing Measurement Report Type subfield 468 is similar to a field defined in IEEE 802.11bf but has new values ​​to indicate that it includes vendor-specific report types. The TBD subfield 472 is similar to a subfield defined in IEEE 802.11bf but may be extended in some embodiments.

[0095] In addition to the sensing measurement types specified in IEEE 802.11bf, the sensing measurement report type subfield 468 in these embodiments can be set to a new specific value (e.g., seven (7) or binary "111") to indicate that a vendor-specific report is included in the sensing measurement setup request frame 440. Table 1 shows the sensing measurement report type subfield 468 in these embodiments, where values ​​0 to 6 correspond to those listed in IEEE 802.11bf, Table 9-401r (where a value of zero (0) represents CSI, and values ​​1 to 6 are reserved), and value 7 is a new specific value used to indicate the use of a vendor-specific report. Of course, in some other embodiments, another suitable value (e.g., any one of reserved values ​​1 to 6) can be used to indicate the use of a vendor-specific report.

[0096] Table 1 – Types of Perception Measurement Reports

[0097] In some embodiments using one or more vendor-specific report types, STA 112 may set the Perception Measurement Report Type subfield 468 of the Perception Measurement Parameter Field 450 in the Perception Measurement Setup Request Frame 440 to a specific value (e.g., 7 (7)) to indicate that a vendor-specific report type can be used, and append the Vendor-Specific Report Sub-Element Field 452 (described in more detail later) to the end of the Perception Measurement Setup Request Frame 440 to specify one or more vendor-specific report types.

[0098] Figure 14 This is a schematic diagram of the structure of a vendor-specific report sub-element field 452 according to some embodiments of the present invention. As shown, the vendor-specific report sub-element field 452 includes: a sub-element ID sub-field 482 (one (1) octet) which can be set to a predefined value (e.g., value 221) to indicate that the perceived type is vendor-specific (i.e., a vendor-specific report is specified; described in more detail below); a length sub-field 484 (one (1) octet) indicating the length of the vendor-specific report sub-element field 452; an OUI sub-field 486 (three (3) octets) specifying the vendor's OUI; and one or more vendor-specific sub-fields 488 (variable size) associated with the OUI for storing information related to the vendor-specific report type. For example, in some embodiments where the vendor can define multiple report types, one or more vendor-specific sub-fields 488 may include a vendor report type field. Any other report-specific parameters defined by the vendor may be included in one or more vendor-specific sub-fields 488.

[0099] Figure 15 A schematic diagram of the structure of a sensing measurement establishment response frame 480 according to some embodiments of the present invention. In this example, the sensing measurement establishment response frame 480 conforms to and is modified according to IEEE 802.11bf clause 9.6.7.50.

[0100] As shown, the Sensing Measurement Establishment Response Frame 480 includes: a Category field 442 (one (1) octet); a Common Action field 444 (one (1) octet); a Dialogue Token field 446 (one (1) octet); a Status Code field 492 (three (3) octets); a Sensing Measurement Parameter field 450 (variable length); and a Vendor-Specific Report Sub-Element field 452 for specifying one or more vendor-specific report types. The Category field 442, Common Action field 444, Dialogue Token field 446, and Status Code field 492 are identical to those defined in IEEE 802.11bf. The Sensing Measurement Parameter field 450 is similar to the fields defined in IEEE 802.11bf, but has new values ​​for indicating the inclusion of vendor-specific report types.

[0101] Category field 442, common action field 444, dialogue token field 446, perception measurement parameter field 450, and vendor-specific report sub-element field 452 are similar to Figure 12 The fields shown in the Perception Measurement Establishment Request Frame 440 are examples. For instance, the Perception Measurement Parameters field 450 may include a Perception Measurement Report Type, which can be set to the value 7 to indicate that a vendor-specific report type is included, and the Vendor-Specific Report Sub-Element field 452 may include the selected vendor-specific report type.

[0102] In the above embodiments, the supplier-specific report sub-element is field 452 of the perception measurement establishment request frame 440 and the perception measurement establishment response frame 480. In some embodiments, a supplier-specific report sub-element may be included as a sub-element or sub-field of the perception measurement parameter field 450 of the perception measurement establishment request frame 440 and / or the perception measurement establishment response frame 480 (e.g., in...). Figure 13 (See “TBD” subfield 472 shown).

[0103] Through the structure of the aforementioned perception measurement establishment request frame 440 and perception measurement establishment response frame 480, perception nodes can easily exchange vendor-specific perception measurement reports.

[0104] In some embodiments, sensing measurement setup frames 440 and 480 may include a list of sensing measurement report types, such as the IEEE 802.11bf default report type and vendor-specific report types, such as those shown in Table 1.

[0105] In these embodiments, the message flow can be similar to Figure 11A or Figure 11B The message flow shown (depending on whether an associated or non-associated sensing session is being established) includes a list of multiple report types indicated by STA 112 in the sensing measurement establishment request frame 440. AP 102 selects a report type from the list and responds with information from the sensing measurement establishment response frame 480.

[0106] Figure 16 This is a schematic diagram of the structure of the perception measurement establishment request frame 440 in these embodiments. The perception measurement establishment request frame 440 and... Figure 12 The perception measurement setup request frame shown is similar, except that the perception measurement setup request frame 440 in these embodiments does not include the vendor-specific report sub-element field 452, but instead includes a simplified report type list field 502 for listing one or more perception measurement report types.

[0107] Figure 17This is a schematic diagram of the structure of the report type list field 502 in the sensing measurement setup request frame 440 of these embodiments. For each measurement report, the report type list field 502 includes one or more report type subfields 512, each of which is similar to a subfield defined in IEEE 802.11bf, but can be used to specify a default report type and a vendor-specific report type. More specifically, as... Figure 18 As shown, each report type subfield 512 includes multiple items, including: an element ID item 522 for storing the unique ID of the report type subfield 512; a length item 524 for indicating the length of the report type subfield 512; an element ID extension item 526 defined in IEEE 802.11bf for extending the number of defined IEEE 802.11 elements; similar to... Figure 13 The perception measurement report type subfield 468 shown includes perception measurement report type item 528; optional OUI item 530 for storage vendor OUI; and perception measurement report item 532. Perception measurement report type item 528 is similar to... Figure 13 The 468 shown can have the values ​​shown in Table 1 (e.g., a value of zero (0) to indicate the default CSI report type or a value of 7 to indicate a single vendor-specific report type). For example, while the perceived measurement report type item 528 has eight (8) bits, three (3) least significant bits (LSB) or three (3) most significant bits (MSB) or any other three suitable bits make it take a value between zero (0) and 7 (7), as described above, and no other bits are used. OUI item 530 is similar. Figure 14 The OUI item 486 shown, and the perception measurement report item 532 are similar to Figure 14 The supplier-specific subfield 488 is shown.

[0108] When the perception measurement report type item 528 has a value of zero (0), the report type subfield 512 does not have an OUI item 530 and a perception measurement report item 532. When the perception measurement report type item 528 has a value of seven (7), the report type subfield 512 has an OUI item 530 that stores the vendor OUI and a perception measurement report item 532 that stores the vendor-specific report type associated with the vendor OUI.

[0109] Figure 19 This is a schematic diagram of the structure of the perception measurement parameter field 450 in the perception measurement establishment request frame 440 and / or perception measurement establishment response frame 480 in these embodiments. The perception measurement parameter field 450 in these embodiments is similar to... Figure 13The difference between the perception measurement parameter field 450 shown in these embodiments and the one shown is that the perception measurement parameter field 450 also includes a report type quantity subfield 504 (one or more bits), the value of which indicates the number of report types in the list encoded in the report type list field 502 of the perception measurement establishment request frame 440.

[0110] More specifically, in some embodiments, if one or more report types are included in the report type list field 502 of the perception measurement establishment request frame 440, the value of the report type quantity subfield 504 is the number of report types specified in the report type list field 502. If no report type is included in the report type list field 502 of the perception measurement establishment request frame 440 (meaning, for example, the default report type will be used), the value of the report type quantity subfield 504 is set to zero (0).

[0111] Table 2 shows the perception measurement report type subfield 468 in these embodiments, where values ​​0 to 5 correspond to those listed in IEEE 802.11bf and Table 9-401r (where a value of zero (0) indicates CSI, and values ​​1 to 5 are reserved), value 6 indicates the presence of multiple report types, and value 7 indicates the use of vendor-specific reports. Of course, in some other embodiments, other suitable values ​​(e.g., any two of reserved values ​​1 to 5) may be used to indicate the inclusion of multiple report types and the use of vendor-specific reports.

[0112] Table 2 – Types of Perception Measurement Reports

[0113] In other embodiments, the report type quantity subfield 504 may be a 1-bit subfield. If no report type is included in the report type list field 502 of the perception measurement establishment request frame 440, the value of the report type quantity subfield 504 is set to zero (0). However, if one or more report types are included in the report type list field 502 of the perception measurement establishment request frame 440, the value of the report type quantity subfield 504 is set to one (1), and the actual number of report types is included in another predefined subfield (e.g., perception measurement report type subfield 468).

[0114] In some embodiments, the perceived measurement parameter field 450 does not include a separate report type quantity subfield 504. Instead, the number of report types may be included in the “TBD” subfield 472.

[0115] In these embodiments, the perception measurement establishment request frame 480 is similar to Figure 15The difference between the perception measurement establishment request frame shown is that the perception measurement establishment request frame 480 in these embodiments may include multiple vendor-specific report sub-element fields 452.

[0116] Using the above structure, the sensing measurement setup frames 440 and 480 in these embodiments allow sensing nodes to exchange lists of sensing measurement reports, including IEEE 802.11bf defaults and vendor-specific reports.

[0117] While the aforementioned sensing measurement setup frames 440 and 480 can be used for sensing with wireless communication signals in any suitable frequency band, these frame structures are particularly well-suited for sub-7 GHz measurements.

[0118] In some embodiments, a vendor-specific perception measurement report may be included in the DMG perception measurement request and response frame. The message flow in these embodiments is typically... Figure 11A or Figure 11B The message flow shown is the same (depending on whether an associated sensing session or a non-associated sensing session is being established). However, since the IEEE 802.11 standard defines separate frame types for sub 7 GHz and DMGCSI measurements, different frames can be used for DMG sensing measurement establishment.

[0119] In DMG, sensing measurement setup frames 440 and 480 have the same structure and are typically represented as DMG sensing measurement setup elements. Figure 20 This is a schematic diagram of the structure of a DMG sensing measurement establishment element 540 according to some embodiments of the present invention. In this example, the DMG sensing measurement establishment element 540 conforms to IEEE 802.11bf. Figure 9-10 02bf was modified.

[0120] As shown, the DMG sensing measurement setup element 540 includes: an element ID field 542 (one (1) octet); a length field 544 (one (1) octet) indicating the length of the DMG sensing measurement setup element 540; an element ID extension field 546 (one (1) octet); a measurement setup control field 548 (three (3) octets); a report type field 550 (four (4) octets); a location configuration information (LCI) field 552 (zero (0) or 16 octets); a peer orientation field 554 (zero (0) to five (5) octets); and an optional sub-element field 556 (variable length). The element ID field 542, length field 544, element ID extension field 546, measurement setup control field 548, LCI field 552, and peer orientation field 554 are the same as those defined in IEEE 802.11bf. The report type field 550 and sub-element field 556 are similar to those fields defined in IEEE 802.11bf, but with extensions as described below.

[0121] When a vendor-specific report type is required, the report type field 550 can be set to indicate a predefined value that includes the vendor-specific report type (see below), and the sub-element field 556 can be included in the DMG-perceived measurement establishment element 540 and include information about the vendor-specific report type.

[0122] Table 3 lists the values ​​of the report type field 550 of the DMG sensing measurement establishment element 540, which corresponds to and modifies IEEE 802.11bf Table 9-401y. More specifically, the value 220 of the report type field 550 indicates a list including multiple report types, and the value 221 of the report type field 550 indicates a single vendor-specific report type. The sub-element field 556 is similar to the vendor-specific sub-element field 452 and can have, for example, the following values: Figure 14 The structure shown.

[0123] Table 3 – Report Type Subfield Definitions (11bf – Table 9-401y)

[0124] In these embodiments, the DMG sensing report element can be used to report sensing measurements, which may require signaling for vendor-specific reports. Figure 21 This is a schematic diagram of the structure of DMG sensing reporting element 580. In this example, DMG sensing measurement establishment element 580 conforms to and is modified according to IEEE 802.11bf clause 9.4.2.238.2.

[0125] As shown, the DMG Sensing Report element 580 includes: an element ID field 582 (one (1) octet); a length field 584 (one (1) octet) indicating the length of the DMG Sensing Report element 580; an element ID extension field 586 (one (1) octet); a DMG Measurement Setup ID field 588 (one (1) octet); a Measurement Burst ID field 590 (one (1) octet); a Sensing Instance Sequence Number (SN) field 592 (one (1) octet); a DMG Sensing Report Type field 594 (one (1) octet); a DMG Sensing Report Control field 596 (three (3) octets); and a DMG Sensing Report field 598 (variable length). The Element ID field 582, Length field 584, Element ID Extension field 586, DMG Measurement Establishment ID field 588, Measurement Burst ID field 590, Sensing Instance SN field 592, DMG Sensing Report Control field 596, and DMG Sensing Report field 598 are the same as those defined in IEEE 802.11bf. The DMG Sensing Report Type field 594 is similar to the fields defined in IEEE 802.11bf, but has new values ​​for indicating vendor-specific report types.

[0126] DMG-Aware Report field 598 includes the vendor OUI and any other parameters related to vendor-specific reports. DMG-Aware Report Type field 594 can have values ​​as shown in Table 3. For example, DMG-Aware Report Type field 594 can have a value 221 to specify that vendor-specific reports can be used. As another example, DMG-Aware Report Type field 594 can have a value 220 to specify a list including vendor-specific report types, allowing the transmission of both standard or general report types and the list of vendor-specific report types together.

[0127] The aforementioned structure of DMG sensing measurement establishment element 540 and DMG sensing report element 580 allows sensing nodes to negotiate vendor-specific DMG sensing measurement report types.

[0128] In some embodiments, the CSI quantification report can be used as a supplier-specific perceived measurement report.

[0129] In these embodiments, after obtaining the complex channel estimate, its phase and amplitude are normalized. The normalized phase and amplitude of the channel estimate are then quantized into corresponding bit sizes with appropriate parameters (e.g., the maximum values ​​of the normalized phase and amplitude, respectively), wherein the bit sizes can be normalized so that scaling factor feedback is not required. The quantized phase and amplitude are compiled into a CSI quantization report for reporting to the sensing initiator 302. These quantization parameters can also be compiled into a CSI quantization report.

[0130] Figure 22 This is a flowchart of an exemplary CSI quantization process 600 performed by the perception responder 304 to generate a CSI quantization report. In this example, the wireless communication signal 114 includes OFDM symbols, and the CSI quantization process 600 is performed on the OFDM symbols.

[0131] After process 600 begins (step 602), the sensing responder 304 obtains a channel estimate, for example, from the channel estimation function block (step 604). Each channel estimate is an amplitude-dependent channel estimate. (where subscript) i (Index representing the channel estimate for each subcarrier) and phase The complex number. As those skilled in the art will understand, the magnitude of the channel estimate. Typically in the range of zero (0) to M m Rayleigh distribution within the range of, where, It is the maximum amplitude, and This indicates the output bit size of the channel estimation function block and the phase of the channel estimate. They are usually evenly distributed in the range between –π and π.

[0132] In step 606, the sensing responder 304 estimates the phase of each channel using the phase maximum value π. Normalization to obtain normalized phase ,Right now , making .

[0133] In step 608, the sensing responder 304 will normalize each phase Quantified as:

[0134] in, Indicates the quantization phase. It is used for normalized phase The size of the quantization bits used for quantization.

[0135] In step 610, the maximum amplitude is used. Magnitude of each channel estimate Normalization, i.e. , making .

[0136] In step 612, the sensing responder 304 will assign each normalized amplitude Quantified as:

[0137] in, Indicates the quantification range, It is used for normalized amplitude The size of the quantization bits used for quantization.

[0138] In step 614, the sensing responder 304 generates a normalized phase. and normalized amplitude The CSI quantization report is generated and sent to the perception initiator 302. In some embodiments, the CSI quantization report may also include necessary parameters, such as the phase quantization bit size. and amplitude quantization bit size .

[0139] Then the CSI quantization process 600 is completed (step 616).

[0140] As those skilled in the art will understand, the phase quantization bit size and amplitude quantization bit size Some parameters can be specified in relevant standards or defined in other ways, while the output bit size of the channel estimation function block... Other parameters may be vendor-specific. In some embodiments, an additional normalization process may be required between the channel estimation function block and the CSI quantization function block to normalize the vendor-specific parameters. Set the value to a standardized value For example, see U.S. Patent Application No. 18 / 134,743, filed April 14, 2023, the contents of which are incorporated herein by reference in their entirety.

[0141] In these embodiments, CSI quantification reports are used as a supplier-specific option to facilitate negotiation.

[0142] In the above description, various embodiments are described with respect to IEEE 802.11bf. In some alternative embodiments, the wireless systems, apparatuses, and methods described herein may be used with respect to other sensing-related standards, such as IEEE 802.15.4ab, ultra-wideband (UWB) sensing standards, and / or cellular sensing standards.

[0143] In the above description, various embodiments are disclosed as examples of wireless systems, apparatuses, and methods for providing WLAN vendor-specific awareness reports using coordinated transmissions between multiple access points, such as: • Methods for establishing, executing, and reporting vendor-specific sensing measurements, applicable to sub 7 GHz and DMG; • A method for negotiating perception session reports between AP 102 and STA 112; • Perception measurement setup frames suitable for establishing supplier-specific perception measurements; • Allows predefined values ​​(e.g., value 7) for supplier-specific or proprietary extended perceived measurement report types. • A method for generating CSI sensing measurement reports to use wireless communication signals for sensing.

[0144] The wireless systems, apparatuses, and methods disclosed herein offer various benefits, such as: • The method used for sensing session report negotiation allows sensing STA 112 to negotiate vendor-specific sensing measurement report types with peer sensing sites (such as other STA 112 and / or AP 102), thereby providing flexibility for sensing reporting.

[0145] • The Sensing Measurement Setup Request Frame 440 and Sensing Measurement Setup Response Frame 480 allow sensing nodes to easily exchange vendor-specific sensing measurement reports.

[0146] • Sensing measurement setup frames 440 and 480 allow sensing nodes to exchange lists of sensing measurement reports, including IEEE 802.11bf defaults and vendor-specific reports.

[0147] • The DMG perception measurement setup element and DMG perception report element allow perception nodes to negotiate vendor-specific DMG perception measurement report types.

[0148] • CSI quantification reports facilitated negotiation as a vendor-specific option.

[0149] Those skilled in the art will understand that the above methods can be implemented in any suitable manner, for example, as computer-executable instructions stored in one or more non-transitory computer-readable storage media, as one or more modules having one or more circuits for performing the above methods, as implemented in one or more chipsets having one or more circuits for performing the above methods, as implemented in one or more devices or apparatuses having one or more circuits for performing the above methods, and so on.

[0150] Those skilled in the art will understand that the above embodiments and / or their features can be customized, separated, and / or combined as needed or desired. Furthermore, while embodiments have been described above with reference to the accompanying drawings, those skilled in the art will understand that variations and modifications can be made without departing from the scope defined by the appended claims.

Claims

1. A computerized method, characterized by, comprising: sending a signal for broadcasting a multi-report type support capability; receiving a first request from a device with an indication of the multi-report type support capability; sending a first response to the device with a confirmation of the multi-report type support capability; exchanging information with the device for selecting a report type; receiving one or more sensing measurement reports generated using the selected report type from the device.

2. The method of claim 1, wherein, The first request is a probe request defined based on an IEEE 802.11 standard, and the first response is a probe response defined based on the IEEE 802.11 standard.

3. The method according to claim 1 or 2, characterized in that, Exchanging information with the device for selecting the report type comprises: sending a request frame, the request frame including one or more sensing measurement report types; receiving a response frame, the response frame including the report type selected from the one or more sensing measurement report types.

4. The method of claim 3, wherein, The one or more sensing measurement report types include a default sensing measurement report type and at least one vendor-specific sensing measurement report type.

5. The method of claim 3, wherein, The one or more sensing measurement report types include at least one first sensing measurement report type associated with a first identifier (ID) and a second sensing measurement report type not associated with any ID.

6. The method according to any one of claims 3 to 5, characterized in that, The request frame includes a first field, the first field including a first predefined value for indicating that the one or more sensing measurement report types are included in the request frame.

7. The method of claim 6, wherein, The request frame is a sensing measurement setup request frame defined based on an IEEE 802.11 standard, and the response frame is a sensing measurement setup response frame defined based on the IEEE 802.11 standard; wherein the first field is a sensing measurement parameter field defined based on the IEEE 802.11 standard; wherein the first predefined value is a value of a sensing measurement report type subfield of the sensing measurement parameter field.

8. The method according to claim 6 or 7, characterized in that, The first predefined value is 7.

9. The method according to any one of claims 6 to 8, characterized in that, The request frame includes a second field, the second field including the one or more sensing measurement report types.

10. The method of claim 9, wherein, The second field further includes: a second ID with a second predefined value; a length subfield for indicating a length of the second field; a third ID.

11. The method of claim 10, wherein, The third ID is an organizationally unique identifier (OUI).

12. The method according to claim 10 or 11, characterized in that, The second predefined value is 221.

13. The method according to any one of claims 9 to 12, characterized in that, The second field further includes one or more subfields, each of the one or more subfields including: a fourth ID; a length item for indicating a length of the subfield; a sensing measurement report type item; a sensing measurement parameter.

14. The method of claim 13, wherein, The first field further includes a number count of the one or more subfields of the second field.

15. The method according to any one of claims 6 to 14, characterized in that, The first predefined value is 6 if the one or more sensing measurement report types include a plurality of sensing measurement report types, or the first predefined value is 7 if the one or more sensing measurement report types include only a single sensing measurement report type.

16. The method according to any one of claims 3 to 15, characterized in that, The response frame comprises a third field comprising a third predefined value indicating that a selected report type is included in the response frame.

17. The method according to any one of claims 3 to 16, characterized in that, The one or more sensing measurement report types comprise a channel state information (CSI) quantization report, the CSI quantization report being generated by the device using a procedure comprising: obtaining a channel estimate value; normalizing a phase of the channel estimate value by π; quantizing the normalized phase; normalizing an amplitude of the channel estimate value by an amplitude maximum value; quantizing the normalized amplitude.

18. A module characterized in that, comprising: one or more circuits for performing the method according to any of claims 1 to 17.

19. One or more non-transitory computer-readable storage media storing instructions that, when executed by one or more processors of a computing system, cause the computing system to perform any one of the methods of claims 1-18. comprising computer executable instructions which, when executed, cause at least one processing unit, at least one processor, or at least one circuit to perform the method according to any of claims 1 to 17.

20. One or more processors, wherein: functionally connected to one or more memories for performing the method according to any of claims 1 to 17.

21. An apparatus, comprising: comprising: one or more processors functionally connected to one or more memories for performing the method according to any of claims 1 to 17.

22. An apparatus comprising: for performing the method according to any of claims 1 to 17.

23. The apparatus of claim 22, wherein, comprising: one or more units for performing the method according to any of claims 1 to 17.

24. A computer-readable storage medium storing a computer program, wherein the computer program comprises instructions that, when executed by a processor of a device, cause the device to perform the method of any one of claims 1-23. when the computer program is executed by the apparatus, cause the apparatus to implement the method according to any of claims 1 to 17.

25. A computer program product, characterised in that, comprising one or more instructions which, when executed by the apparatus, cause the apparatus to implement the method according to any of claims 1 to 17.

26. A computer program, characterized in that, when the computer program is executed by the computer, cause the apparatus to implement the method according to any of claims 1 to 17.

27. A communication system, characterized by comprising a communication node for performing the method according to any of claims 1 to 17.

Images