Sensing method, and communication apparatus

Abstract

The embodiments of the present application are applied to a wireless local area network system that supports 802.11-series protocols, such as the next-generation Wi-Fi protocol of IEEE 802.11ax, i.e., 802.11be (Wi-Fi 7 / EHT), and the next generation of 802.11be, i.e., Wi-Fi 8, UHR and Wi-Fi AI, and may be further applied to a UWB-based wireless personal area network, a sensing system, etc. Provided in the embodiments of the present application are a sensing method, and a communication apparatus. In the method, a first AP may send a first request frame to one or more APs, which first request frame is used by an AP to request a plurality APs to perform joint sensing. By means of the method, the first AP can use sensing results from the other APs, thereby preventing a sensing task failure caused by a sensing result from the first AP being unavailable when the first AP performs sensing independently.

Description

Perception method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on July 29, 2023, with application number 202310952356.4 and application name “Perception Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communications, and in particular, to a perception method and a communication device. Background Art

[0003] When an access point (AP) senses a target in an overlapping basic service set (OBSS), it may be subject to interference from other devices in the space, such as co-channel or adjacent-channel interference. Furthermore, since the sensing target is at the edge of the basic service set (BSS), the sensing performance is poor, resulting in large errors in the measurement results. However, the AP will continue to perform sensing measurements in the time window used for sensing measurements as long as the communication link is not interrupted. Only after receiving a sensing measurement report and performing signal processing using a certain algorithm can the AP learn that the sensing measurement result has a large error and can only abandon the measurement result, causing the sensing task to fail. Therefore, the AP can request multiple other APs to perform sensing measurements on its behalf, that is, multiple APs perform joint sensing. When the sensing results of one AP are unavailable, the sensing results of other APs can be used.

[0004] However, the current Sensing by Proxy (SBP) only allows non-AP STAs to request APs to perform sensing measurements on their behalf. That is, the existing SBP can only be initiated by STAs and does not support APs requesting AP proxy sensing. Therefore, a multi-AP joint proxy sensing solution cannot be implemented based on the current SBP.

[0005] Summary of the Invention

[0006] The present application provides a perception method and a communication device, which can avoid the situation where the perception task fails due to the unavailability of the perception result when the AP perceives alone.

[0007] In a first aspect, a sensing method is provided. The method may be executed by a communication device, or may be executed by a component of the communication device (e.g., a chip or circuit), without limitation. For ease of description, the following description is based on an example of a first AP performing the sensing method.

[0008] The method includes: a first AP sends first request frames corresponding to N APs to N APs respectively, the first request frames are used for the AP to initiate a multi-AP joint proxy perception request, and N is a positive integer; the first AP receives first response frames from the N APs respectively, and the first response frames are used to indicate acceptance of the multi-AP joint proxy perception request.

[0009] In the above technical solution, the first AP can send a first request frame to N APs to request one or more APs to perform joint perception. This method enables the first AP to utilize the perception results of one or more APs, thereby avoiding the failure of the perception task when the first AP perceives alone because the perception results are unavailable.

[0010] It should be noted that the multi-AP joint proxy perception in this scheme may be multiple APs performing joint perception of the same target, or the multi-AP joint proxy perception may be separate perceptions of different parts of the same target. The first AP may obtain the perception result of the entire target based on the perception results of different APs, or the multi-AP joint proxy perception may be a joint perception of the environment. This application does not specifically limit the perception target of the multi-AP joint perception.

[0011] In certain implementations of the first aspect, the first request frame includes first information, the first information indicating that the first request frame is a request frame for the AP to initiate multi-AP joint proxy perception, and the first information is carried in the first request frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0012] It can be understood that in this technical solution, for the device that receives the first request frame, it can be determined based on the first information in the first request frame that the device type of the device that initiates the multi-AP joint proxy awareness request is an AP.

[0013] In certain implementations of the first aspect, the first request frame includes second information, the second information includes parameters required by the second AP to perform multi-AP joint proxy perception, and the second AP is the AP that receives the first request frame.

[0014] In certain implementations of the first aspect, the parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: an expiration time for multi-AP joint perception, a multi-AP collaborative transmission type, a trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

[0015] In some implementations of the first aspect, the first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0016] In certain implementations of the first aspect, the method further includes: the first AP receives a second request frame from the first site STA, where the second request frame is used by the STA to initiate a multi-AP joint proxy awareness request; the first AP sends a second response frame to the first STA, where the second response frame indicates acceptance of the multi-AP joint proxy awareness request.

[0017] It should be understood that the first request frame sent by the first AP to the N APs is sent based on the received second request frame.

[0018] In the above technical solution, the first STA can initiate a multi-AP joint proxy perception request to the first AP to instruct the first AP to initiate a multi-AP joint proxy perception request to other APs. This method enables the first AP to utilize the perception results of one or more APs, thereby avoiding the failure of the perception task when the first AP alone acts as a proxy for the first STA because the perception result is unavailable.

[0019] In certain implementations of the first aspect, the second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for the STA to initiate multi-AP joint proxy awareness, and the fourth information is carried in the second request frame. Included in the public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0020] It can be understood that in this technical solution, for the device that receives the second request frame, the device type of the device that initiates the multi-AP joint proxy awareness request can be determined based on the fourth information in the second request frame as STA.

[0021] In some implementations of the first aspect, the second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

[0022] In certain implementations of the first aspect, the parameters required for multi-AP joint proxy perception include one or more of the following parameters: an expiration time for multi-AP joint perception, a multi-AP cooperative transmission type, a detection phase type based on a trigger, the number of APs required to establish multi-AP joint proxy perception, whether the required number of APs is mandatory, whether the AP receiving the second request frame needs to perform perception measurements, the required number of perception response STAs, whether the number of perception response STAs is mandatory, whether the AP receiving the second request frame is recommended to perform joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

[0023] In some implementations of the first aspect, when the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, where the sixth information includes the perception parameters allocated to each of the recommended APs.

[0024] In certain implementations of the first aspect, the sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for perception, the number of required perception response STAs, whether the number of perception response STAs is mandatory, and the type of trigger-based detection phase.

[0025] In certain implementations of the first aspect, the second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the STA, and the seventh information is carried in the second response frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0026] In certain implementations of the first aspect, the method further includes: the first AP triggering N APs to perform multi-AP joint sensing measurement.

[0027] In certain implementations of the first aspect, if a second AP among the N APs is not the last AP among the N APs to be triggered to perform perception measurement, the first AP triggers the N APs to perform multi-AP joint perception measurement, including: the first AP determines that the second AP completes the perception measurement; the first AP sends a first inquiry trigger frame to a third AP among the N APs, where the first inquiry trigger frame is used to trigger the third AP to perform perception measurement, and the third AP is any AP among the N APs that has not been triggered to perform perception measurement; and the first AP receives a first inquiry response frame from the third AP.

[0028] In the above technical solution, it can be considered that the first AP sequentially triggers N APs to perform perception measurements. For example, after AP#1 among the N APs currently triggered by the first AP completes the perception measurement, the first AP sends a query trigger frame to AP#2 among the N APs to trigger AP#2 to perform perception measurements. After AP#2 completes the perception measurement, the first AP continues to send query trigger frames to AP#3 among the N APs to trigger AP#3 to perform perception measurements, until all APs among the N APs triggered by the first AP complete perception measurements.

[0029] For example, in this triggered measurement method, the first AP can control the perception measurements of multiple APs to be performed sequentially at very short time intervals. For example, this time length is generally in microseconds. For example, this time interval can be a SIFS interval. At this time, the perception results of each AP can be considered to be soft-synchronized. When the perception results of the first AP are unavailable due to interference or weak BSS edge signal strength, the perception results of N APs at the "same moment" can be used to avoid the failure of the perception task.

[0030] In certain implementations of the first aspect, a first AP triggers N APs to perform multi-AP joint perception measurement, including: the first AP sends a second query trigger frame to the N APs, where the second query trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start times and durations; and the first AP receives second query response frames from the N APs, where the second query response frames instruct the APs to confirm performing the perception measurement based on the corresponding perception measurement start times and durations.

[0031] In the above technical solution, it can be seen that the first AP can allocate a perception measurement start time and duration for each of the N APs, and the N APs perform perception measurements based on their own perception measurement start time and duration.

[0032] In certain implementations of the first aspect, the second inquiry trigger frame includes eighth information, where the eighth information includes a start time and a duration for the N APs to perform perception measurements.

[0033] In certain implementations of the first aspect, ninth information in the first inquiry trigger frame is used to trigger the AP receiving the first inquiry trigger frame to perform multi-AP joint sensing measurement, and the ninth information is carried in the sensing trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the first inquiry trigger frame.

[0034] In some implementations of the first aspect, the first inquiry trigger frame includes tenth information, where the tenth information instructs the third AP to start performing perception measurement.

[0035] In certain implementations of the first aspect, the eleventh information in the second inquiry trigger frame is used to trigger N APs to perform multi-AP joint sensing measurement, and the eleventh information is carried in the sensing trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

[0036] In certain implementations of the first aspect, the second inquiry trigger frame includes twelfth information, where the twelfth information instructs the N APs to perform perception measurement based on their respective corresponding perception measurement start times and durations.

[0037] In certain implementations of the first aspect, the method further includes: the first AP sending a first report trigger frame to N APs, where the first report trigger frame is used to trigger the N APs to report measurement results of multi-AP joint perception; and the first AP receiving measurement results from the N APs.

[0038] In certain implementations of the first aspect, the method further includes: the first AP sending measurement results of N APs to the first STA.

[0039] In certain implementations of the first aspect, the thirteenth information in the first report trigger frame is used to trigger the AP receiving the first report trigger frame to report the measurement results of multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

[0040] In a second aspect, a communication method is provided. The method may be executed by a communication device, or may be executed by a component of the communication device (e.g., a chip or circuit), without limitation. For ease of description, the following description is based on an example of execution by a second AP.

[0041] The method includes: a second AP receives a first request frame from a first AP, the first request frame is used for the AP to initiate a multi-AP joint proxy perception request, the second AP is any AP among N APs for which the first AP requests multi-AP joint proxy perception, N is an integer; the second AP sends a first response frame to the first AP, the first response frame is used to indicate acceptance of the multi-AP joint proxy perception request.

[0042] For the beneficial effects of the second aspect, please refer to the description of the first aspect and will not be repeated here.

[0043] In some implementations of the second aspect, the first request frame includes first information, the first information indicating that the first request frame is a request frame for the AP to initiate multi-AP joint proxy perception, and the first information is carried in the first request frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0044] In some implementations of the second aspect, the first request frame includes second information, where the second information includes parameters required for the second AP to perform multi-AP joint proxy perception.

[0045] In certain implementations of the second aspect, the parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: an expiration time for multi-AP joint perception, a multi-AP collaborative transmission type, a trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

[0046] In some implementations of the second aspect, the first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0047] In certain implementations of the second aspect, the method further includes: the second AP performing multi-AP joint sensing measurement under triggering by the first AP.

[0048] In certain implementations of the second aspect, the second AP performs multi-AP joint perception measurement under the triggering of the first AP, including: the second AP receives a third inquiry trigger frame from the first AP, where the third inquiry trigger frame is used to trigger the second AP to perform perception measurement; and the second AP sends a third inquiry response frame to the first AP.

[0049] In certain implementations of the second aspect, a first AP triggers N APs to perform multi-AP joint perception measurement, including: a second AP receives a second inquiry trigger frame from the first AP, where the second inquiry trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start times and durations; and the second AP sends a second inquiry response frame to the first AP, where the second inquiry response frame instructs the second AP to confirm that the perception measurement is to be performed based on the corresponding perception measurement start time and duration.

[0050] In certain implementations of the second aspect, the second inquiry trigger frame includes eighth information, where the eighth information includes a start time and a duration for the N APs to perform perception measurements.

[0051] In certain implementations of the second aspect, the fourteenth information in the third inquiry trigger frame is used to trigger the second AP to perform multi-AP joint sensing measurement, and the fourteenth information is carried in the sensing trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the first inquiry trigger frame.

[0052] In certain implementations of the second aspect, the third inquiry trigger frame includes fifteenth information, and the fifteenth information instructs the second AP to start performing perception measurement.

[0053] In certain implementations of the second aspect, the eleventh information in the second inquiry trigger frame is used to trigger N APs to perform multi-AP joint sensing measurement, and the eleventh information is carried in the sensing trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

[0054] In certain implementations of the second aspect, the second inquiry trigger frame includes twelfth information, where the twelfth information instructs the N APs to perform perception measurement based on their respective corresponding perception measurement start times and durations.

[0055] In certain implementations of the second aspect, the method further includes: the second AP receiving a first report trigger frame from the first AP, the first report trigger frame being used to trigger the second AP to report a measurement result of multi-AP joint perception; and the second AP sending the measurement result to the first AP.

[0056] In certain implementations of the second aspect, the thirteenth information in the first report trigger frame is used to trigger the reception of the second AP to report the measurement result of the multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

[0057] In a third aspect, a communication method is provided. The method may be executed by a communication device, or may be executed by a component of the communication device (e.g., a chip or circuit), without limitation. For ease of description, the following description is based on an example of execution by a first STA.

[0058] The method includes: a first STA sends a second request frame to a first access point AP, where the second request frame is used for the STA to initiate a multi-AP joint proxy perception request; the first STA receives a second response frame from the first AP, where the second response frame indicates acceptance of the multi-AP joint proxy perception request.

[0059] For the beneficial effects of the third aspect, please refer to the description of the first aspect and will not be repeated here.

[0060] In certain implementations of the third aspect, the second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for the STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the second request frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0061] In certain implementations of the third aspect, the second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

[0062] In certain implementations of the third aspect, the parameters required for multi-AP joint proxy perception include one or more of the following parameters: an expiration time for multi-AP joint perception, a multi-AP cooperative transmission type, a trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the required number of APs is required, whether the AP receiving the second request frame needs to perform perception measurements, the required number of perception response STAs, whether the number of perception response STAs is required, whether the AP receiving the second request frame is recommended to perform joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

[0063] In certain implementations of the third aspect, when the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, where the sixth information includes the perception parameters allocated to each of the recommended APs.

[0064] In certain implementations of the third aspect, the sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for perception, the number of required perception response STAs, whether the number of perception response STAs is mandatory, and the type of trigger-based detection phase.

[0065] In some implementations of the third aspect, the second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to the multi-AP joint proxy perception request initiated by the STA, and the seventh information is carried in the second response frame. Included public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0066] In certain implementations of the third aspect, the method further includes: the first STA receiving a measurement result of multi-AP joint perception from the first AP.

[0067] In a fourth aspect, a communication device is provided, which is used to execute the method provided in any one of the first to third aspects above. Specifically, the communication device may include a unit and / or module for executing the method provided in the first aspect or any one of the above-mentioned implementations of the first aspect, or include a unit and / or module for executing the method provided in the second aspect or any one of the above-mentioned implementations of the second aspect, or include a unit and / or module for executing the method provided in the third aspect or any one of the above-mentioned implementations of the third aspect, such as a processing unit and / or a transceiver unit.

[0068] In one implementation, the communication apparatus is a device (e.g., a first station, a first access point, or a second access point). When the communication apparatus is a device, the transceiver unit may be a transceiver or an input / output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input / output interface may be an input / output circuit.

[0069] In another implementation, the communication device is a chip, chip system, or circuit used in a device (e.g., a first station, a first access point, or a second access point). When the communication device is a chip, chip system, or circuit used in a device, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0070] In a fifth aspect, a communication device is provided, which includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or to execute the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or to execute the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0071] In one implementation, the communication apparatus is a device (eg, a first station, a first access point, or a second access point).

[0072] In another implementation, the apparatus is a chip, a chip system, or a circuit used in a device (eg, a first station, a first access point, or a second access point).

[0073] In a sixth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0074] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as processor output, reception, input and other operations, and can also be understood as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0075] In the seventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes instructions for executing the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or includes instructions for executing the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or includes instructions for executing the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0076] In an eighth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is caused to execute the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or the computer is caused to execute the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or the computer is caused to execute the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0077] In the ninth aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface, executes the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or executes the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or executes the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0078] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored on the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by the above-mentioned first aspect or any one of the above-mentioned implementation methods of the first aspect, or execute the method provided by the above-mentioned second aspect or any one of the above-mentioned implementation methods of the second aspect, or execute the method provided by the above-mentioned third aspect or any one of the above-mentioned implementation methods of the third aspect.

[0079] In a tenth aspect, a communication system is provided, comprising the above-mentioned first station, first access point and second access point. BRIEF DESCRIPTION OF THE DRAWINGS

[0080] FIG1 is a schematic diagram of a network architecture of a wireless local area network applicable to an embodiment of the present application.

[0081] FIG2 is a schematic diagram of the WLAN Sensing process defined by IEEE 802.11bf.

[0082] FIG3 is a schematic diagram of a triggered sensing measurement exchange process.

[0083] FIG4 is a schematic diagram of TB sensing measurement exchange performed by an AP and a STA.

[0084] FIG5 is a flow chart of SBP.

[0085] FIG6 is a schematic flowchart of a perception method provided by the present application.

[0086] FIG7 is a schematic diagram of a possible frame structure of a first request frame proposed in this application.

[0087] FIG8 is a schematic structural diagram of the Co-Sensing Parameters Control field in the first request frame proposed in this application.

[0088] FIG9 is a schematic diagram of a possible frame structure of a first response frame proposed in this application.

[0089] FIG10 is a schematic diagram of a frame structure of a possible second request frame proposed in this application.

[0090] FIG11 is a schematic structural diagram of the Co-SBP Parameters Control field in the second request frame proposed in this application.

[0091] FIG12 is a schematic structural diagram of the MAP Parameters Control field in the second request frame proposed in this application.

[0092] FIG13 is a schematic diagram of a frame structure of a possible second response frame proposed in this application.

[0093] FIG14 is a schematic diagram of the multi-AP joint sensing process corresponding to scenario 1.

[0094] FIG15 is a schematic diagram of the multi-AP joint sensing process corresponding to scenario 2.

[0095] FIG16 is a schematic diagram of joint perception performed by multiple APs based on implementation method one.

[0096] FIG17 is a schematic diagram of joint perception performed by multiple APs based on implementation method 2.

[0097] FIG18 is a schematic diagram of a possible frame structure of a Co-SBP Polling Trigger frame proposed in this application.

[0098] FIG19 is a schematic diagram of the structure of the User Info List field in the Co-SBP Polling Trigger frame proposed in this application.

[0099] Figure 20 is a schematic block diagram of a communication device 200 provided in an embodiment of the present application.

[0100] Figure 21 is a schematic block diagram of a communication device 300 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0101] The technical solution in this application will be described below with reference to the accompanying drawings.

[0102] The embodiments of the present application can be applied to wireless local area networks (WLANs). Currently, WLANs adopt the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards. A WLAN may include multiple basic service sets (BSSs). The network nodes in a BSS are access points (APs) and non-AP STAs (hereinafter referred to as STAs).

[0103] Figure 1 is a schematic diagram of the network architecture of a wireless local area network applicable to an embodiment of the present application. As shown in (a) in Figure 1, a BSS may include an AP and one or more STAs associated with the AP. The network architecture of a wireless local area network may also include multiple BSSs, for example, as shown in (b) in Figure 1, which shows two BSSs, which partially overlap with each other, namely OBSS. Among them, BSS#1 includes AP#1, STA11, STA12 and STA13, and BSS#2 includes AP#2, STA21, STA22 and STA23. STA11, STA12, STA22, and STA23 are the overlapping parts of the two BSSs. Each BSS consists of an AP and multiple STAs. Within a BSS, data can be transmitted between the AP and each STA. Communication can also be carried out between AP#1 and AP#2.

[0104] An access point is a terminal (e.g., a mobile phone) that connects to a wired (or wireless) network. It's typically deployed in homes, buildings, and campuses, with a typical coverage radius of tens to hundreds of meters. It can also be deployed outdoors. An access point acts as a bridge between wired and wireless networks, connecting wireless network clients and then connecting the wireless network to the Ethernet.

[0105] Specifically, the AP can be a terminal or network device with a Wi-Fi chip, and the network device can be a server, a router, a switch, a bridge, a computer, a mobile phone, a relay station, a vehicle-mounted device, a wearable device, a network device in a 5G network, a network device in a future 6G network, or a network device in a public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto. The access point can be a device that supports the Wi-Fi standard. For example, the access point can also support one or more standards of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.

[0106] A STA may be a wireless communication chip, a wireless sensor, or a wireless communication terminal, and may also be referred to as a user, user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. A STA may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, an Internet of Things device, a wearable device, a terminal device in a 5G network, a terminal device in a future 6G network, or a terminal device in a PLMN, and the embodiments of the present application are not limited thereto. A STA may be a device that supports the WLAN standard. For example, the STA may support one or more standards of the IEEE 802.11 family, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.

[0107] For example, STAs can be mobile phones, tablets, set-top boxes, smart TVs, smart wearable devices, in-vehicle communication devices, computers, Internet of Things (IoT) nodes, sensors, smart homes such as smart cameras, smart remote controls, smart water and electricity meters, and sensors in smart cities.

[0108] The above-mentioned AP or STA may include a transmitter, a receiver, a memory, a processor, etc., wherein the transmitter and the receiver are used for sending and receiving packet structures respectively, the memory is used to store signaling information and store preset values ​​agreed in advance, etc., and the processor is used to parse signaling information, process related data, etc.

[0109] It should be understood that Figure 1 is only exemplary and should not limit the network architecture of the wireless local area network to which the present application is applicable. For example, the network architecture may also include more BSSs, each BSS may also include more STAs, or the area where multiple BSSs overlap may also include more STAs, etc. The embodiments of the present application are not limited here.

[0110] WLAN sensing is a promising technology that leverages widely deployed WLAN devices and specific WLAN signals to perform sensing tasks. WLAN signals can reflect, refract, or penetrate surfaces during propagation. By receiving WLAN signal echoes and performing appropriate signal processing using algorithms, the received WLAN signals can be used to perceive the surrounding environment, detect obstacles, or monitor moving targets.

[0111] The IEEE 802.11bf protocol defines a unified WLAN sensing process, enabling devices to obtain channel state information (CSI) between two or more devices, thereby achieving environmental awareness. IEEE 802.11bf covers identified sensing scenarios by introducing different roles for participating devices, which can be summarized as follows: a sensing initiator is a device that initiates WLAN sensing; a sensing responder is a device that responds to WLAN sensing initiated by a sensing initiator; a sensing transmitter is a device that transmits a null data packet (NDP); and a sensing receiver is a device that receives the NDP sent by the sensing transmitter and performs sensing measurements based on the NDP.

[0112] Figure 2 is a schematic diagram of the WLAN Sensing process defined by IEEE 802.11bf. In the sensing capabilities exchange phase, device sensing capability information is exchanged; in the sensing measurement session phase, the sensing initiator and sensing responder negotiate WLAN sensing operation information through request / respond frames; in the sensing measurement exchange phase, the sensing transmitter and sensing receiver perform sensing measurements through NDP frames; and in the sensing measurement termination phase, the corresponding WLAN Sensing settings are terminated. Sensing measurement exchanges are divided into trigger-based (TB) sensing measurement exchanges and non-TB sensing measurement instances. TB sensing measurement exchanges are an AP-centric mechanism, with the AP acting as the sensing initiator and one or more STAs acting as sensing responders.

[0113] Figure 3 is a schematic diagram of the triggered sensing measurement exchange process. The process includes a polling phase, a null data packet announcement (NDPA) sounding phase, a trigger frame (TF) sounding phase, and a reporting phase. It should be noted that a triggered sensing measurement exchange should not consist solely of a reporting phase, nor should it consist solely of an NDPA sounding phase, nor should it consist solely of a polling phase and a reporting phase. The following describes the process. In the polling phase, the AP first sends a Sensing Polling Trigger frame to one or more STAs that intend to participate in the sensing measurement. The STA responds with a reflexive Clear to Send (CTS) (CTS-to-self) frame to confirm participation in the subsequent sensing measurement. After polling, the AP will initiate NDPA sounding and / or TF sounding based on the roles negotiated in the sensing measurement session. During the NDPA sounding phase, the AP, acting as a sensing transmitter, sends a Sensing NDPA frame. After a short interframe space (SIFS) interval, the AP then sends an SI2SR NDP frame. STAs, acting as sensing receivers, receive the SI2SR NDP frame and perform sensing measurements. During the TF sounding phase, the AP, acting as a sensing receiver, sends a Sensing SR2SI Sounding Trigger frame to trigger one or more STAs, acting as sensing transmitters, to send SR2SI NDP frames to the AP for sensing measurements. After the sounding phase, the AP triggers the STAs to return sensing measurement results using a Sensing Report Trigger frame.

[0114] Figure 4 shows a TB sensing measurement exchange between an AP and a STA. During a sensing window, the AP and STA need to perform N sensing measurement exchanges. As long as the communication link remains connected, the AP and STA1 complete these N sensing measurement exchanges and then return a sensing measurement report.

[0115] In one possible scenario, when an AP senses a target within an OBSS, it may experience interference from other devices in the space, such as co-channel or adjacent-channel interference. Furthermore, since the target is located at the edge of the BSS, perception performance is poor, resulting in significant measurement errors. However, as long as the communication link remains intact, the sensing measurement exchange continues. Only after receiving the sensing measurement report and performing signal processing using a specific algorithm can the significant error in the sensing measurement result be detected. In this case, multiple sensing measurement exchange results may become unusable, forcing the measurement results to be discarded, resulting in the failure of the sensing task.

[0116] Figure 5 illustrates the SBP process. SBP allows STAs to request the AP to perform sensing measurements on their behalf. First, STA1, acting as the SBP initiator, sends an SBP Request frame to the AP, acting as the SBP responder. The AP then responds to STA1's request with an SBP Response frame. After accepting STA1's SBP request, the AP, acting as the sensing initiator, searches for a suitable STA within the BSS to complete WLAN sensing. After completing WLAN sensing, the AP returns the measurement results to STA1 using an SBP Report frame.

[0117] Therefore, multiple APs can perform joint sensing of the same target. When the sensing result of one AP is unavailable, the sensing results of other APs can be used. However, the existing SBP does not support AP requesting AP proxy sensing, that is, it is impossible to establish multi-AP joint sensing based on the existing SBP.

[0118] In view of this, the present application proposes a sensing method that can achieve multi-AP joint sensing. When the sensing result of a certain AP is unavailable, the sensing results of other APs can be used. The method proposed in the present application is described in detail below with reference to FIG6.

[0119] Figure 6 is a schematic flow chart of a perception method provided by the present application. The method includes the following steps.

[0120] S601: A first AP sends first request frames corresponding to N APs to each of N APs. The first request frames are used by the AP to initiate a multi-AP joint proxy awareness request, where N is a positive integer. Correspondingly, the N APs receive the first request frames from the first AP.

[0121] For the convenience of description, this application may refer to multi-AP joint proxy sensing as coordinated sensing by proxy (Co-SBP).

[0122] It should be noted that the multi-AP joint proxy perception in this scheme may be multiple APs performing joint perception of the same target, or the multi-AP joint proxy perception may be separate perceptions of different parts of the same target. The first AP may obtain the perception result of the entire target based on the perception results of different APs, or the multi-AP joint proxy perception may be a joint perception of the environment. This application does not specifically limit the perception target of the multi-AP joint perception.

[0123] Optionally, since the first AP needs to perform multi-AP joint perception with multiple APs, the first AP in this application can select M (M is greater than or equal to N) APs in the multi-AP cooperation set based on its own needs or other conditions, and send a first request frame to each of the M APs. The N APs in this application can be regarded as the APs that ultimately participate in the multi-AP joint perception. It should be noted that any AP in the multi-AP cooperation set can obtain relevant information of all APs in the multi-AP cooperation set.

[0124] Optionally, the first request frame includes first information, and the first information indicates that the first request frame is a request frame for the AP to initiate multi-AP joint proxy perception, that is, for the device that receives the first request frame, the device type of the device that initiates the Co-SBP request can be determined based on the first information in the first request frame as AP.

[0125] Optionally, the first request frame includes second information, and the second information includes parameters required for the second AP to perform multi-AP joint proxy perception, and the second AP is the AP that receives the first request frame. For example, the parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP cooperative transmission type, trigger-based detection phase type, required number of perception response STAs, and whether the number of perception response STAs is required. The meaning of each parameter will be explained in detail in conjunction with Figure 7, and will not be described here.

[0126] Optionally, the first request frame may further include information on the type of the perception measurement result of the second AP. The second AP obtains the corresponding measurement result based on the type information. The second AP is the AP that receives the first request frame. For example, the first request frame may include one or more types of information. For example, the type of the perception measurement result may be a CSI matrix.

[0127] S602: N APs send their respective first response frames to the first AP, where the first response frames are used to indicate acceptance of the multi-AP joint proxy awareness request. Correspondingly, the first AP receives the first response frames from the N APs.

[0128] For example, N APs can respectively determine whether they can accept the Co-SBP request of the first AP based on their own capabilities and the capabilities of the associated STAs, and directly reply to the first AP in the first response frame. For example, AP#1 among the N APs determines that it can accept the Co-SBP request of the first AP, and then sends a first response frame to the first AP. The first response frame indicates that AP#1 receives the Co-SBP request of the first AP, and then AP#1 establishes a sensing measurement session. It can be understood that establishing a sensing session here means that AP#1 establishes a sensing session with its associated STA to prepare for AP#1 to perform joint sensing measurements. For example, AP#1 can send a sensing measurement request (SensingMeasurementRequest) frame to the associated STA#1, and STA#1 sends a sensing measurement response (SensingMeasurementResponse) frame to AP#1 to indicate whether the sensing session is successfully established.

[0129] For example, AP#1 among the N APs may also first attempt to establish a perception measurement session, and then reply to the first AP according to the result of the session establishment.

[0130] This application does not impose any restrictions on the order in which AP#1 establishes the perception measurement session and replies to the first response frame. The interval between the first request frame and the first response frame does not exceed 20ms.

[0131] Optionally, the first response frame includes third information, where the third information indicates that the first response frame is a response frame for responding to a multi-AP joint proxy awareness request initiated by the AP.

[0132] Optionally, the embodiment of the present application can be applied to the following two scenarios. The processes of the two scenarios are briefly described below.

[0133] Scenario 1: The first AP can proactively initiate a Co-SBP request to N APs based on its own needs. For ease of description, this application refers to the first AP in this scenario as the Co-sensing initiator and the N APs as Co-sensing responders.

[0134] Scenario 2: The first STA can actively initiate a Co-SBP request to the first AP based on its own needs, and the first AP passively initiates a Co-SBP request to N APs based on the request of the first STA. It can be seen that two Co-SBP requests are initiated in Scenario 2. For the convenience of distinguishing the description, this application refers to the device that initiates the first Co-SBP request in this scenario (i.e., the first STA) as the Co-SBP initiator, and the first AP that responds to the Co-SBP request of the first STA as the Co-SBP responder. Afterwards, the first AP will initiate a second Co-SBP request to N APs. Therefore, this application refers to the device that initiates the second Co-SBP request (i.e., the first AP) as the Co-sensing initiator, and the N APs that respond to the Co-SBP request of the first AP as Co-sensing responders.

[0135] It should be understood that S601 and S602 can be regarded as the process corresponding to the Co-SBP request in Scenario 1 or the process corresponding to the second Co-SBP request in Scenario 2. Optionally, if the corresponding scenario is Scenario 2, the first STA also needs to initiate the first Co-SBP request before the first AP initiates the second Co-SBP request. For the process of the first STA initiating the first Co-SBP request, please refer to the description in S603 and S604, which will not be elaborated here.

[0136] Figure 7 is a schematic diagram of the frame structure of a possible first request frame proposed in this application. The first request frame can be regarded as an SBP Request (request) frame redesigned on the basis of the existing SBP Request (request) frame for AP to request multi-AP joint perception. The existing SBP Request frame cannot support the scenario of multi-AP joint perception of this application, and cannot implement the indication of multi-AP joint perception parameters. The first request frame given in Figure 7 can support the scenario of multi-AP joint perception of this application and implement the function of allocating joint perception parameters to each AP. For example, the first request frame can be referred to as a Co-sensing Request (Request) frame in this application.

[0137] It should be understood that the number of bits occupied by each field in the request frame and response frame given in the drawings of the embodiments of the present application is only an example and should not constitute a limitation on the frame structure or frame length of the request frame and response frame proposed in this application.

[0138] It should also be understood that the names of the request frames and response frames and the names of the fields included in the drawings of the embodiments of the present application are merely examples and should not constitute a limitation on the request frames and response frames proposed in this application.

[0139] As shown in Figure 7, the first request frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Measurement Session ID Indication field, a Co-Sensing Parameters Element field, a Sensing Measurement Parameters Element field, and a Responding STA (RSTA) Availability Window element field. The following describes some of the fields in the first request frame that are relevant to this application.

[0140] (1) The first request frame adds a new frame type to the existing SBP Request frame, indicating that the first request frame is an SBP Request frame used by the AP to initiate a multi-AP joint perception request, and indicates that this frame will allocate joint perception parameters to the AP receiving the frame. Exemplarily, the present application extends a frame type in the Public Action / Protected Dual of Public Action field of the existing SBP Request frame to indicate that the frame is a first request frame. Exemplarily, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is 62 (i.e., an example of the first information), it indicates that the current SBP Request frame is a first request frame.

[0141] Table 1

[0142] (2) The Measurement Session ID Indication field in the first request frame indicates the Measurement Session ID, which identifies the perception measurement parameters to be used in the corresponding perception measurement exchange. The existing field is directly reused here and will not be repeated here.

[0143] (3) The RSTA Availability Window element field in the first request frame is the specific time and period allocated by the first AP to N APs for multi-AP joint sensing, that is, the available time window. Multi-AP joint sensing needs to be performed within this allocated time window.

[0144] (4) In the first request frame, the Sensing Measurement Parameters Element field indicates the specific sensing parameters allocated to AP#1 receiving the first request frame. For example, this field includes the bandwidth (BW) field, the maximum (Max) transmit (TX) space-time stream (STS) and the maximum receive (RX) STS fields, and the number of receive antennas (Number of RX Antennas) field. The BW field is used to indicate the sensing measurement bandwidth, the Max TX STS and Max RX STS fields are used to indicate the maximum space-time stream, and the Number of RX Antennas field is used to indicate the number of antennas used by the sensing receiver. In a possible implementation, this field can be designed in the same way as the Sensing Measurement Parameters Element field in the existing SBP Request frame.

[0145] (5) A new Co-Sensing Parameter element field is defined in the first request frame.

[0146] It should be noted that the naming of the newly added fields in the first request frame is only an example for the convenience of description. If the information carried and the functions implemented in a field are the same as the information carried and the functions implemented by the newly added fields given in this application, then the field can be considered to be the same field as the newly added fields given in this application. The specific names given for the newly added fields in the first request frame or other frames later are also examples, and the relevant places will not be repeated one by one later.

[0147] It should also be noted that the length of the newly added field in the first request frame is only an example for the convenience of description, and the length of this field should not constitute a limitation to the present invention. The specific length of the newly added field given in the first request frame or other frames later is also an example, and the relevant parts will not be repeated one by one later.

[0148] As shown in Figure 7, the Co-sensing Parameter element field includes an element identification (Element ID) field, a length (Length) field, an element identification extension (Element IDExtension) field, a joint sensing parameter control (Co-SensingParametersControl) field, a sensing responder address (Sensing Responder Addresses) field, and a sensing responder identification field (Sensing Responder IDs) field. The following describes some fields in the Co-sensing Parameter element field that are relevant to this application.

[0149] 1) The Element ID field and Element ID Extension field in the Co-sensing Parameter element field are used to jointly indicate the type and usage scenario of the corresponding element. This application extends the Element ID Extension to indicate that this element carries the joint sensing parameters allocated to AP#1 receiving the first request frame. The Element ID, Length, and Element ID Extension in this application follow the design of IEEE 802.11bf. For example, as shown in Table 2, an element type is extended on the Element ID. When the value of Element ID Extension is<Last assigned+18> When , it is considered that the element carries the joint sensing parameters allocated to AP#1 that receives the first request frame.

[0150] Table 2

[0151] 2) The Co-SensingParametersControl field in the Co-sensing Parameter element field is used to carry the second information. For example, Figure 8 is a schematic diagram of the structure of the Co-SensingParametersControl field. The Co-Sensing ParametersControl field includes a joint sensing request (Co-Sensing Request) field, a joint sensing procedure expiry index (Co-Sensing Procedure Expiry Exponent) field, a multi-AP transmission type (MAP Transmission Model) field, a detection phase type (Sounding Phase Model) field, a sensing responder number (Number of Sensing Responder field), whether the number of sensing responders must be (mandatory or mandatory) (Mandatory Number of Responder field), a recommended responder list (PreferredResponderList), a recommended responder number (Number ofPreferredResponders), whether the recommended responder number must be (MandatoryPreferredResponder) and a sensing responder to sensing responder (SR2SR) sensing request (SR2SRSoundingRequest). The following describes in detail the meaning of each field in the Co-SensingParametersControl field and which parameters in the second information it carries.

[0152] The Co-Sensing Request field is used to indicate in which frame the Co-Sensing Parameters element is carried. Exemplarily, the Co-Sensing Request field is set to "1" to indicate that the Co-Sensing Parameters element is carried in the request frame for multi-AP joint perception initiated by the AP, and is set to "0" to indicate that the Co-Sensing Parameters element is carried in the response frame for multi-AP joint perception initiated in response to the AP. It should be noted that since the first request frame is a request frame for multi-AP joint perception initiated by the AP, the value of this field in the first request frame is 1. In addition, the first response frame also includes this field (see Figure 9). Since the first response frame is a response frame for multi-AP joint perception initiated in response to the AP, the value of this field in the first response frame is 0. Since the Public Action / Protected Dual of Public Action field in the first request frame already indicates that the first request frame is a request frame for multi-AP joint perception initiated by the AP, this field in the first request frame may be an optional field.

[0153] The Co-Sensing Procedure Expiry Exponent field is used by the AP that obtains this field to determine whether to terminate multi-AP joint sensing (i.e., the expiration time of multi-AP joint sensing that carries the second information in this field). Co-Sensing Procedure Expiry Exponent contains an unsigned integer, which can indicate the length of time. Within the time window agreed upon by multi-AP joint sensing, the AP that obtains this field starts counting down the duration indicated by this field after listening to the frame in the channel. When the countdown ends, there is still no frame interaction in the channel, and the AP considers that the current multi-AP joint sensing process is over. Exemplarily, the value of this field can be 2(Co-SBP Procedure Expiry Exponent+8) milliseconds.

[0154] The MAP Transmission Model field indicates the multi-AP collaborative transmission type to support multiple APs to coordinate the transmission of frames in the perception measurement process. For example, this field can indicate different transmission types through 2 bits. For example, when the MAP Transmission Model field is 00 (i.e., the value is 0), it indicates that the multi-AP collaborative transmission type is coordinated beamforming (CBF), and N APs can send frames in the perception measurement process based on CBF. The present application is not limited to CBF. In the future, multi-AP collaborative transmission methods suitable for the present application can be indicated by other values ​​in the MAP Transmission Model field.

[0155] The Sounding Phase Model field indicates the TB Sounding Phase type established by the AP that receives the first request frame. For example, this field can indicate different TB sounding phases through 2 bits. For example, when the Sounding Phase Model field is 00 (i.e., the value is 0), the AP#1 that receives the first request frame can only choose to establish the NDPA sounding phase; when the Sounding Phase Model field is 01 (i.e., the value is 1), the AP#1 that receives the first request frame can only choose to establish the TF sounding phase; when the Sounding Phase Model field is 10 (i.e., the value is 2), AP#1 can choose between the NDPA sounding phase and the TF sounding phase.

[0156] It is understood that the above method of indicating the sounding phase type through the Sounding Phase Model field is merely an example, and this application does not exclude other methods for indicating the sounding phase type. For example, this application may also indicate the sounding phase type by assigning transmitter / receiver roles to different Sensing Responders through the "Sensing Responder Role Bitmap" field in the existing SBP, but this application does not limit this method.

[0157] The Number of Sensing Responder field indicates how many Sensing Responders the AP#1 receiving the first request frame needs to establish sensing (that is, the number of required sensing responder STAs carrying the second information in this field).

[0158] The Mandatory Number of Responder field indicates whether the number of Sensing Responders indicated in the Number of Sensing Responder field is mandatory. For example, this field can be indicated by 1 bit. When the Mandatory Number of Responder field is "0", it means that the number of STAs indicated in the Number of Sensing Responder field is optional. The number of STAs can be regarded as a reference quantity and can be met as much as possible. On the contrary, when the Mandatory Number of Responder field is "1", it means that the number of STAs indicated in the Number of Sensing Responder field must meet the requirements.

[0159] The PreferredResponderList field indicates whether a recommended Sensing Responder list is provided for AP#1 receiving the first request frame. For example, if the Preferred Responder List field is "1", it means that a recommended Sensing Responder list is provided for AP#1, and the address information of the recommended Sensing Responder is carried in the Co-sensing Parameter element in the first request frame (carried in the Sensing Responder Addresses field of the first request frame). AP#1 needs to search for a STA in the recommended Sensing Responder list to initiate a sensing request; if the Preferred Responder List field is "0", it means that no Sensing Responder is recommended for AP#1, and AP#1 searches for a suitable STA in its own BSS to initiate a sensing request.

[0160] The Number of Preferred Responders field indicates the number of Sensing Responders recommended for AP#1 to receive the first request frame. Specifically, if the PreferredResponderList field is "1," the Number of Preferred Responders field indicates the number of recommended Sensing Responder media access control (MAC) addresses contained in the Sensing Responder Addresses field. If the Preferred Responder List field is "0," this field is reserved. For example, all characters in this field can be set to 0, and AP#1 does not read this field.

[0161] The Mandatory Preferred Responder field indicates whether the Sensing Responder recommended for AP#1 receiving the first request frame is mandatory. For example, this field can be indicated by 1 bit. When the Mandatory Preferred Responder field is "0", it indicates that the recommended Sensing Responder is not mandatory. The recommended Sensing Responder can be regarded as a reference, and the Sensing Responder that ultimately participates in sensing should be found among the recommended Sensing Responders as much as possible. On the contrary, when the Mandatory Preferred Responder field is "1", it indicates that the Sensing Responder that ultimately participates in sensing must be found among the recommended Sensing Responders.

[0162] The SR2SRSoundingRequest field indicates whether SR2SR awareness needs to be established. For example, a value of "0" in the SR2SRSoundingRequest field indicates that SR2SR awareness is not required, and a value of "1" indicates that SR2SR awareness is required.

[0163] 3) The Sensing Responder Addresses field in the Co-sensing Parameter element field carries the address information of the Sensing Responder recommended for AP#1 receiving the first request frame. It is understood that the Sensing Responder Addresses field is present in the first request frame only when the PreferredResponderList field indicates that a Sensing Responder is recommended for AP#1. In this case, the Sensing Responder Addresses field contains one or more MAC addresses indicating the MAC addresses of the STAs with which AP#1 establishes awareness.

[0164] 4) The Sensing Responder IDs field in the Co-sensing Parameter element field occupies 0 bits.

[0165] A possible first request frame proposed in FIG. 7 is described in detail above. As an example, a possible frame structure of a first response frame is described below in conjunction with FIG. 9 .

[0166] Figure 9 is a schematic diagram of the frame structure of a possible first response frame proposed in the present application. For example, the first request frame can be referred to as a Co-sensing response (Reponse) frame in the present application. As shown in Figure 9, the frame structure of the first response frame is basically the same as that of the first request frame. Specifically, the first response frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Measurement Session ID Indication field, a Status Code field, a Co-Sensing Parameters Element field, and a Sensing Measurement Parameters Element. Only the fields that carry different information between the first response frame and the first request frame are described here.

[0167] (1) The first response frame extends a frame type in the Public Action / Protected Dual of Public Action field to indicate that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP. Exemplarily, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is "63" (i.e., an example of the first information), it indicates that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP.

[0168] (2) The Status Code field in the first response frame indicates whether AP#1, which receives the first request frame, accepts the request in the first request frame. For example, if AP#1 accepts the request, the Status Code field is set to SUCCESS; if AP#1 rejects the request, the Status Code field is set to REQUEST_DECLINED or REJECTED_WITH_SUGGESTED_CHANGES (identical to the existing Status Code field in 11bf).

[0169] (3) A new Co-Sensing Parameter element field is defined in the first response frame. The design of the Co-Sensing Parameter element field in the first response frame is the same as that in the first request frame, with only some fields having different meanings. The following describes only the fields with different meanings.

[0170] 1) If the Co-Sensing Request field in the Co-Sensing Parameter Control field of the Co-Sensing Parameters Element field of the first response frame exists, illustratively, the value of the Co-Sensing Request field is 1, indicating that the Co-Sensing Parameters element is carried in the request frame for multi-AP joint perception initiated by the AP, and the value is 0, indicating that the Co-Sensing Parameters element is carried in the response frame for multi-AP joint perception initiated in response to the AP, then the value of this field in the first response frame needs to be set to 0, indicating that the Co-Sensing Parameters element is carried in the first response frame. Since the Public Action / Protected Dual of Public Action field in the first response frame already indicates that the first response frame is a response frame for multi-AP joint perception initiated in response to the AP, this field in the first response frame can be an optional field. 2) The Co-Sensing Procedure Expiry Exponent field, MAP Transmission Model field, Sounding Phase Model field, Mandatory Number of Responder field, Mandatory Preferred Responder field, and SR2SR Sounding Request field are reserved in the first response frame. For example, when these characters are reserved, these fields can all be set to 0, and the first AP does not need to read these fields.

[0171] 3) The Number of Sensing Responder field has different meanings depending on the Status Code field. For example, if the Status Code field of the first response frame is equal to SUCCESS, the Number of Sensing Responder field is used to indicate how many Sensing Responders AP#1, which received the first request frame, actually established. If the Status Code field of the first response frame is equal to REJECTED_WITH_SUGGESTED_CHANGES, the Number of Sensing Responder field is used to recommend the value of this field carried in the first request frame the next time the first AP initiates multi-AP joint sensing.

[0172] 4) The PreferredResponderList field indicates the Sensing Responder included in the perception established by AP#1 that receives the first request frame. Specifically, this field is used to indicate whether the Sensing Responder Addresses field and the Sensing Responder IDs field exist. For example, if the Preferred Responder List field is "1", it means that the Sensing Responder Addresses field and the Sensing Responder IDs field exist and contain the address and ID of the Sensing Responder included in the perception established by AP#1 that receives the first request frame; if the Preferred Responder List field is "0", it means that the Sensing Responder Addresses field and the Sensing Responder IDs field do not exist.

[0173] 5) The Number of Preferred Responders field indicates the number of MAC addresses contained in the Sensing Responder Addresses field. For example, if the Preferred Responder List field is "1," the Number of Preferred Responders field indicates the number of Sensing Responder MAC addresses contained in the Sensing Responder Addresses field. If the Preferred Responder List field is "0," this field is reserved.

[0174] (4) The Sensing Responder Addresses field carries the address information of the Sensing Responder selected by AP#1, which receives the first request frame, to satisfy the first AP's request. It is understood that the Sensing Responder Addresses field appears only when the Preferred Responder List field is set to "1." In this case, the Sensing Responder Addresses field contains one or more MAC addresses that indicate the STAs selected by AP#1 to satisfy the first AP's request.

[0175] (5) The Sensing Responder IDs field exists only when the Preferred Responder List field is set to "1" and the Status Code field is equal to SUCCESS. The Sensing Responder IDs field is used to carry the ID information of the Sensing Responder used by AP#1 that receives the first request frame to satisfy the first AP's request, such as the association identification (AID) / unassociated STA identifier (USID). The order of the AID / USID should be the same as the order of the MAC addresses in the Sensing Responder Addresses field.

[0176] In the above technical solution, the first AP can initiate a Co-SBP request to other APs, allowing the first AP to use multiple sensing results simultaneously, thereby avoiding the situation where the sensing task fails due to unavailable sensing results when the first AP senses alone.

[0177] From the above, it can be seen that if the corresponding scenario is scenario 2, the first STA also needs to initiate the first Co-SBP request before the first AP initiates the second Co-SBP request. Then, optionally, before S602, the method also includes S603 and S604.

[0178] S603: The first STA sends a second request frame to the first AP, where the second request frame is used by the STA to initiate a multi-AP joint proxy awareness request. Correspondingly, the first AP receives the second request frame from the first STA.

[0179] It should be understood that the first request frame sent by the first AP to the N APs in S601 is determined and sent based on the received second request frame.

[0180] For example, the second request frame may carry an identifier of an AP recommended by the first STA to the first AP for participating in multi-AP joint perception. The AP recommended by the first STA includes the N APs in S601, and the N APs are the APs among the recommended APs that ultimately participate in multi-AP joint perception.

[0181] For example, if the first STA does not recommend an AP to participate in multi-AP joint perception to the first AP, the first AP can select M (M is greater than or equal to N) APs in the multi-AP collaboration set to initiate multi-AP joint perception. The N APs in S601 are the APs among the M APs that ultimately participate in multi-AP joint perception.

[0182] Optionally, the second request frame includes fourth information, and the fourth information indicates that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, that is, for a device that receives the second request frame, the device type of the device that initiates the Co-SBP request can be determined based on the fourth information in the second request frame as STA.

[0183] Optionally, the second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception. For example, the parameters required for multi-AP joint proxy perception include one or more of the following parameters: multi-AP cooperative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, whether the required number of APs is mandatory, whether the AP receiving the second request frame needs to perform perception measurement, the required number of perception response STAs, whether the number of perception response STAs is mandatory, whether the AP receiving the second request frame is recommended to perform joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

[0184] For example, when the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, which includes perception parameters assigned to each of the recommended APs. For example, the sixth information includes one or more of the following parameters assigned to each recommended AP: measurement parameters for perception, the number of required perception response STAs, whether the number of perception response STAs is required, and the type of trigger-based detection phase. The meaning of each parameter is detailed below in Figure 9 and is not further described here.

[0185] It should be understood that when different perception parameters are provided for the recommended AP in the second request frame, the perception parameters in the first request frame sent by the first AP to AP#1 among the recommended APs are determined based on the perception parameters of AP#1 carried in the second request frame. For example, if the second request frame indicates that the type of detection phase that AP#1 needs to establish is the NDPA sounding phase, and the number of perception response STAs required for AP#1's perception measurement is 5 and this number 5 is a condition that must be met, then the first request frame sent by the first AP to AP#1 also needs to indicate that the type of detection phase that AP#1 needs to establish is the NDPA sounding phase, and the number of perception response STAs required for AP#1's perception measurement is 5 and this number 5 is a condition that must be met.

[0186] Optionally, the second request frame may further include information on the type of the perception measurement result. It should be noted that the type information in the first request frame is the same as the type information in the second request frame.

[0187] S604: The first AP sends a second response frame to the first STA, where the second response frame indicates that the multi-AP joint proxy awareness request is accepted.

[0188] For example, the first AP can determine whether the multi-AP joint perception request of the first STA is feasible through the multi-AP cooperation set information, and reply to the second response frame according to the judgment result. If the second response frame indicates that the request of the first STA is accepted, the first AP establishes multi-AP joint perception with the N APs. For the process of establishing multi-AP joint perception with the N APs, refer to the description in S601 and S602, which will not be repeated here.

[0189] For example, the first AP may also first establish perception with the M APs recommended or determined by the first STA, and then reply with a second response frame to the first STA based on the perception establishment result. For the process of the first AP establishing perception with the M APs recommended or determined by the first STA, please refer to the description in S601 and S602, which will not be repeated here.

[0190] This application does not impose any restrictions on the order in which the first AP establishes perception with the M APs and replies to the second response frame, as long as the interval between the second request frame and the second response frame does not exceed 20ms.

[0191] Optionally, the second response frame includes seventh information, and the seventh information indicates that the second response frame is a response frame for responding to the multi-AP joint proxy awareness request initiated by the STA.

[0192] Figure 10 is a schematic diagram of the frame structure of a possible second request frame proposed in this application. The second request frame can be regarded as an SBP Request frame redesigned based on the existing SBP Request frame for STAs to request multi-AP joint perception. For example, the second request frame can be referred to as a Co-SBPRequest frame in this application.

[0193] As shown in Figure 10, the second request frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Co-SBP Parameters Element field, a Sensing Measurement Parameters Element field, and an Availability Window element field for the initiating STA (ISTA). The following describes some of the fields in the second request frame that are relevant to this application.

[0194] (1) The second request frame adds a new frame type to the existing SBP Request frame, indicating that the first request frame is an SBP Request frame used by the STA to initiate a multi-AP joint perception request, and indicates that this frame will carry multi-AP joint perception parameters. Exemplarily, the present application extends a frame type in the Public Action / Protected Dual of Public Action field of the existing SBP Request frame to indicate that the frame is a second request frame. Exemplarily, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is "60" (i.e., an example of the fourth information), it indicates that the current SBP Request frame is a second request frame.

[0195] (2) The ISTA Availability Window element in the second request frame is used by the first STA to inform the first AP of its idle time period. The first AP needs to allocate the time and period for multi-AP joint sensing during this idle time period. This is the same as the existing SBP design and is reused here.

[0196] (3) The Sensing Measurement Parameters Element in the second request frame indicates the specific sensing parameters allocated to the first AP receiving the second request frame. For example, this field includes the BW field, the Max TXSTS and Max RXSTS fields, and the Number of RX Antennas field. For the meaning of each field, refer to the description of the corresponding field in the Sensing Measurement Parameters Element field in the first request frame, which is not repeated here. In one possible implementation, this field can have the same design as the Sensing Measurement Parameters Element field in the existing SBP Request frame.

[0197] (4) A new Co-SBP Parameter element field is designed in the second request frame.

[0198] As shown in Figure 10, the Co-SBP Parameter element field includes an element identification (Element ID) field, a length (Length) field, an element identification extension (Element IDExtension) field, a joint agent perception parameter control (Co-SBPParametersControl) field, a multi-AP parameter control (MAPParametersControl) field, a perception responder address (Sensing Responder Addresses) field, and a perception responder identification field (Sensing Responder IDs) field. The following describes some fields in the Co-SBP Parameter element field that are relevant to this application.

[0199] 1) The Element ID field and Element ID Extension field in the Co-SBP Parameter element field are used to jointly indicate the type and usage scenario of the corresponding element. This application extends the Element ID Extension to indicate that this element carries multi-AP joint perception parameters. The Element ID, Length, and Element ID Extension in this application follow the design of IEEE 802.11bf. For example, as shown in Table 2, an element type is extended on the Element ID. When the value of Element ID Extension is<Last assigned+17> When , it is considered that the corresponding element carries the multi-AP joint perception parameters.

[0200] 2) The Co-SBPParametersControl field in the Co-SBP Parameter element field is used to carry the fifth information. For example, Figure 11 is a schematic diagram of the structure of the Co-SBPParametersControl field. The Co-SBP Parameters Control field includes a joint proxy perception request (Co-SBP Request) field, a joint proxy perception procedure expiry index (Co-SBP Procedure Expiry Exponent) field, a multi-AP transmission type (MAP Transmission Model) field, a detection phase type (Sounding Phase Model) field, an AP number (Number of AP) field, an AP number must (Mandatory Number of AP) field, a joint proxy perception initiator (Co-SBP Initiator) field, a sensing responder number (Number of Sensing Responder) field and a sensing responder number must (Mandatory Number of Responder) field, a recommended AP list (Preferred AP List) field, a recommended AP number (Number of Preferrd AP) field, a recommended AP different perception element (Different Sensing element of Preferred AP) field, a sensing responder (Sensing Responder) field, a recommended responder list (Preferred Responder The following describes in detail the meaning of each field in the Co-SBPParametersControl field and which parameters in the fifth information it carries.

[0201] The Co-SBP Request field is used to indicate in which frame the Co-SBP Parameters element is carried. Exemplarily, the Co-SBP Request field is set to "1" to indicate that the Co-SBP Parameters element is carried in the request frame for multi-AP joint perception initiated by the STA, and is set to "0" to indicate that the Co-SBP Parameters element is carried in the response frame for multi-AP joint perception initiated in response to the STA. It should be noted that since the second request frame is a request frame for multi-AP joint perception initiated by the STA, the value of this field in the second request frame is 1. In addition, the second response frame also includes this field (see Figure 13). Since the second response frame is a response frame for multi-AP joint perception initiated in response to the STA, the value of this field in the second response frame is 0. Since the Public Action / Protected Dual of Public Action field in the second request frame already indicates that the second request frame is a request frame for multi-AP joint perception initiated by the STA, this field in the second request frame can be an optional field.

[0202] For descriptions of the Co-SBP Procedure Expiry Exponent field, the MAP Transmission Model field, and the Sounding Phase Model field, refer to the descriptions of the corresponding fields in the first request frame, which will not be repeated here.

[0203] However, it should be noted that the value of the Co-Sensing Procedure Expiry Exponent field in the first request frame should be the same as the value of the Co-SBP Procedure Expiry Exponent in the second request frame, that is, the first AP and the N APs determine whether the multi-AP joint perception process is ended based on the same parameter value. Within the time window agreed upon by the multi-AP joint perception, the first STA and the first AP that obtain this field start counting down the duration indicated by this field after monitoring the frame in the channel. When the countdown ends, there is still no frame interaction in the channel, and the first STA and the first AP consider that the current multi-AP joint perception process is ended.

[0204] It should be noted that the value of the MAP Transmission Model field in the first request frame should be the same as the value of the MAP Transmission Model field in the second request frame.

[0205] The Number of AP field indicates how many APs are required for multi-AP joint perception, that is, the first STA can use the Number of AP field to indicate to the first AP how many APs are required for establishing multi-AP joint perception.

[0206] The Mandatory Number of APs field indicates whether the number of APs indicated in the Number of APs field is mandatory. For example, if the Mandatory Number of APs field is "0," it indicates that the number of APs indicated in the Number of APs field is optional. In this case, the number of APs indicated in the Number of APs field is a reference quantity and should be met whenever possible. Conversely, if the Mandatory Number of APs field is "1," it indicates that the number of APs indicated in the Number of APs field is mandatory.

[0207] The Co-Sensing Initiator field indicates whether the first AP requested by the first STA to establish multi-AP joint sensing needs to perform sensing measurements. For example, a value of "0" in the Co-SBP Initiator field indicates that it is not required, and a value of "1" indicates that it is required.

[0208] The Number of Sensing Responders field indicates how many Sensing Responders the first AP needs to establish awareness of. It should be noted that this field only exists when the Co-Sensing Initiator field is "1".

[0209] The Mandatory Number of Responder field indicates whether the number of Sensing Responders indicated in the above-mentioned Number of Sensing Responder field is mandatory.

[0210] The Preferred AP List field indicates whether a recommended AP list is provided for the first AP. For example, if the Preferred AP List field is "1," it indicates that a recommended AP list is provided for the first AP, and the MAC address of the recommended AP is carried in the MAP Parameters of the second request frame. The AP needs to search for an AP in the recommended AP list to initiate a second Co-SBP request. If the Preferred AP List field is "0," it indicates that no recommended AP list is provided for the first AP. The first AP searches for a suitable AP among all APs participating in multi-AP collaboration to initiate a second Co-SBP request.

[0211] The Number of Preferred APs field indicates the number of recommended APs provided for the first AP. Specifically, if the Preferred AP List field is "1," the Number of Preferred APs field indicates how many MAP Parameters Control fields the Co-SBP Parameters Element field contains, each corresponding to a recommended AP. If the Preferred Responder List field is "0," this field is retained.

[0212] The Different Sensing element of Preferred AP field indicates whether different sensing parameters are provided for the recommended AP. It should be noted that the Different Sensing element of Preferred AP field is meaningful only when the Preferred AP List is "1." For example, if the Different Sensing element of Preferred AP field is "1," it indicates that different parameters are assigned to the recommended AP; if the Different Sensing element of Preferred AP field is "0," it indicates that the recommended AP uses the same parameters, which are the same as those provided to the first AP.

[0213] It should be noted that, if the first STA does not recommend an AP for the first AP, the AP participating in the multi-AP joint sensing found by the first AP itself uses the same parameters, which are the same as the parameters sent by the first STA to the first AP.

[0214] It can be understood that if the Different Sensing element of Preferred AP field is "0," when the first AP needs to send a first request frame to AP#1 among the recommended APs, the first AP generates the first request frame and sends it to AP#1 based on the information obtained in the second request frame. For example, the frame structure of the first request frame is shown in FIG7 . Then, the Sensing Measurement Parameters field in the Sensing Measurement Parameters element field of the first request frame carries the information carried in the Sensing Measurement Parameters field in the Sensing Measurement Parameters element field of the second request frame, and the Number of Sensing Responders field, Mandatory Number of Sensing Responders field, and Sounding Phase Model field in the Co-SBP Parameters Control field of the first request frame respectively carry the information carried in the Number of Sensing Responders field, Mandatory Number of Sensing Responders field, and Sounding Phase Model field in the Co-SBP Parameters Control field of the second request frame.

[0215] The Sensing Responder field indicates whether the first STA participates in the multi-AP joint sensing process as a sensing responder. For example, a value of "0" in the Sensing Responder field indicates non-participation, and a value of "1" indicates participation. It is understandable that when the Sensing Responder field indicates that the first STA participates in the multi-AP joint sensing measurement, the Co-Sensing Initiator field should indicate that the first AP needs to perform sensing.

[0216] For descriptions of the Preferred Responder List field, the Number of Preferred Responders field, the Mandatory Preferred Responder field, and the SR2SR Sounding Request field, please refer to the description of the corresponding fields in the first request frame and will not be repeated here. It should be noted that these four fields are parameters allocated to the first AP, that is, these four fields are meaningful only when the Co-Sensing Initiator field indicates that the first AP needs to perform sensing measurements, otherwise they are retained.

[0217] 3) The MAPParametersControl field in the Co-SBP Parameter element field is used to carry the sixth information. For example, FIG12 is a schematic diagram of the structure of the MAPParametersControl field. The MAPParametersControl field includes the Preferred AP Addresses field, the Preferred AP IDs field, the Sensing Measurement Parameters field, the Number of Sensing Responders field, the Mandatory Number of Sensing Responders field, the Sounding Phase Model field, the Preferred Responder List field, the Number of Preferred Responders field, the Mandatory Preferred Responder field, the SR2SR Sounding Request field, the Sensing Responder Addresses field, and the Sensing Responder IDs field. The following describes in detail the meaning of each field in this field and which parameters in the sixth information it carries.

[0218] The Preferred AP Addresses field carries the address information of the recommended AP. It should be understood that the MAPParameters Control field is present in the second request frame only when the Preferred AP List field is set to a recommended AP. In this case, the Preferred AP Addresses field in the MAPParameters Control field contains a MAC address indicating the MAC address of the recommended AP. It should be understood that each Preferred AP Addresses field in the MAPParametersControl field corresponds to a different recommended AP.

[0219] It should be noted that the Preferred AP IDs field in the second request frame occupies 0 bits.

[0220] The Sensing Measurement Parameters field is used to assign sensing parameters to different APs. For example, this field includes the BW field, the Max TXSTS and Max RXSTS fields, and the Number of RX Antennas field. For the meaning of each field, refer to the description of the corresponding field in the Sensing Measurement Parameters Element field in the first request frame and are not repeated here. In one possible implementation, this field can have the same design as the Sensing Measurement Parameters field in the Sensing Measurement Parameters Element in the existing SBP Request frame.

[0221] The Number of Sensing Responders field indicates how many Sensing Responders (ie, sensing response STAs) should be included in the sensing established by different recommended APs.

[0222] The Mandatory Number of Sensing Responders field indicates whether the number of Sensing Responders indicated in the Number of Sensing Responders field is mandatory.

[0223] The Sounding Phase Model field indicates the TB Sounding Phase type that the AP of the corresponding AID needs to establish during the perception phase. The design concept of this field is the same as that of the Sounding Phase Model field of the Co-SBP Parameters Control field, except that the objects indicated are different.

[0224] For descriptions of the Preferred Responder List field, the Number of Preferred Responders field, the Mandatory Preferred Responder field, the SR2SR Sounding Request field, the Sensing Responder Addresses field, and the Sensing Responder IDs field, refer to the descriptions of the corresponding fields in the first request frame and are not repeated here. It should be noted that these four fields are parameters allocated to the second AP, that is, these four fields are meaningful only when the Different Sensing element of Preferred AP field indicates that different sensing parameters are provided for the recommended AP; otherwise, they are retained.

[0225] It can be understood that if the first STA assigns different sensing parameters to different recommended APs via the MAP Parameters Control field in the second request frame, then when the first AP needs to send a first request frame to AP#1 among the recommended APs, the first AP needs to obtain the information carried in the MAP Parameters Control field for AP#1 among the recommended APs and then generate the first request frame to be sent to AP#1 based on this information. For example, the frame structure of the first request frame is shown in FIG7 . Then, the Sensing Measurement Parameters field in the Sensing Measurement Parameters element field of the first request frame carries the sensing parameters assigned to AP#1 by the Sensing Measurement Parameters field in the MAP Parameters Control field, and the Number of Sensing Responders field, Mandatory Number of Sensing Responders field, and Sounding Phase Model field in the Co-Sensing Parameters Control field of the first request frame carry the sensing parameters assigned to AP#1 by the Number of Sensing Responders field, Mandatory Number of Sensing Responders field, and Sounding Phase Model field in the MAP Parameters Control field, respectively. 4) The Sensing Responder Addresses field in the Co-SBP Parameter element field carries the address information of the Sensing Responder recommended for the first AP. It is understood that the Sensing Responder Addresses field is present in the second request frame only when the Preferred Responder List field is set to recommend a Sensing Responder and the Co-Sensing Initiator field indicates that the first AP needs to perform sensing measurements. In this case, the Sensing Responder Addresses field contains one or more MAC addresses, which indicate the MAC addresses of the STAs with which the first AP establishes sensing.

[0226] 5) The Sensing Responder IDs field in the Co-SBP Parameter element field occupies 0 bits.

[0227] A possible second request frame proposed in FIG. 10 is described in detail above. As an example, a possible frame structure of a second response frame is described below in conjunction with FIG. 13 .

[0228] Figure 13 is a schematic diagram of the frame structure of a possible second response frame proposed in this application. For example, the second request frame can be referred to as a Co-SBP response (Reponse) frame in this application. As shown in Figure 13, the frame structure of the second response frame is basically the same as that of the second request frame. Specifically, the second response frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Status Code field, an AID / USID field, a Co-SBPParametersElement field, a SensingMeasurementParametersElement field, and an RSTA Availability Window element field. Only the fields that carry different information in the second response frame and the second request frame are described here.

[0229] (1) The second response frame extends a frame type in the Public Action / Protected Dual of Public Action field to indicate that the second response frame is a response frame for responding to a multi-AP joint proxy awareness request initiated by a STA. Exemplarily, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is 61 (ie, an example of the seventh information), it indicates that the second response frame is a response frame for responding to a multi-AP joint proxy awareness request initiated by a STA.

[0230] (2) The Status Code field in the second response frame indicates whether the first AP receives the request in the second request frame. For an example of this field, please refer to the above description and will not be repeated here.

[0231] It should be noted here that if the Status Code field is equal to SUCCESS and the first STA is associated with the first AP, the AID / USID field is set to the AID of the first STA; if the Status Code field is equal to SUCCESS and the first STA is not associated with the first AP, the AID / USID field is set to the USID of the first STA.

[0232] (3) The second response frame defines a new Co-SBP Parameter element field. The Co-SBP Parameter element field in the second response frame is designed identically to the Co-SBP Parameter element field in the second request frame, with only some fields having different meanings. The following describes only the fields with different meanings.

[0233] 1) If the Co-SBP Request field of the Co-SBP Parameter Control field of the Co-SBP Parameters Element field of the second response frame exists, illustratively, the value of the Co-SBPRequest field is 1, indicating that the Co-Sensing Parameters element is carried in the request frame for multi-AP joint perception initiated by the STA, and the value is 0, indicating that the Co-Sensing Parameters element is carried in the response frame for multi-AP joint perception initiated in response to the STA, then the value of this field in the second response frame needs to be set to 0, indicating that the Co-SBP Parameters element is carried in the second response frame. Since the Public Action / Protected Dual of Public Action field in the second response frame already indicates that the second response frame is a response frame for multi-AP joint perception initiated in response to the AP, this field in the second response frame can be an optional field.

[0234] 2) The Co-SBP Procedure Expiry Exponent field, MAP Transmission Model field, Sounding Phase Model field, Mandatory Number of AP field, Co-Sensing Initiator field, Mandatory Number of Responder field, Sensing Responder field, Mandatory Preferred Responder field, SR2SR Sounding Request field, and Different Sensing element of Preferred AP field are retained in the second response frame.

[0235] 3) Number of APs has different meanings depending on the Status Code field. For example, if the Status Code field of the second response frame is equal to SUCCESS, the Number of APs field is used to indicate how many APs the AP receiving the second request frame actually established for multi-AP joint perception. If the Status Code field of the second response frame is equal to REJECTED_WITH_SUGGESTED_CHANGES, the Number of APs field is used to recommend the value of this field carried in the second request frame when the first STA initiates multi-AP joint perception next time.

[0236] 4) The Number of Sensing Responder field has different meanings depending on the Status Code field. For example, if the Status Code field of the second response frame is equal to SUCCESS, the Number of Sensing Responder field is used to indicate how many Sensing Responders the AP receiving the second request frame has actually established. If the Status Code field of the second response frame is equal to REJECTED_WITH_SUGGESTED_CHANGES, the Number of Sensing Responder field is used to recommend the value of this field carried in the second request frame the next time the first STA initiates multi-AP joint sensing. It should be noted that this field will only exist in the second response frame if it exists in the second request frame.

[0237] 5) The Preferred AP List field indicates whether the MAP Parameters Control field carries the AIDs of the APs included in the first AP's awareness or the MAC addresses of the APs recommended by the first AP for STA4. This field indicates whether the MAP Parameters Control field exists. For example, a value of "1" in the Preferred Responder List field indicates the presence of the MAP Parameters Control field; a value of "0" in the Preferred Responder List field indicates the absence of the MAP Parameters Control field. In one possible implementation, this field can have the same design as the Preferred Responder List field in the existing SBP Response frame.

[0238] 6) The Number of Preferred APs field indicates the number of MAP Parameters Control fields included. For example, if the Preferred AP List field is "1," the Number of Preferred APs field indicates the number of MAP Parameters Control fields included, where one MAP Parameters Control field corresponds to one recommended AP. If the Preferred Responder List field is "0," this field is reserved.

[0239] 7) The Number of Preferred Responders field indicates the number of MAC addresses contained in the Sensing Responder Addresses field. For example, if the Preferred Responder List field is "1," the Number of Preferred Responders field indicates the number of Sensing Responder MAC addresses contained in the Sensing Responder Addresses field. If the Preferred Responder List field is "0," this field is reserved.

[0240] (4) The second response frame defines a new MAP Parameters Control field. The MAP Parameters Control field in the second response frame is designed identically to the MAP Parameters Control field in the second request frame, with only some fields having different meanings. The following describes only the fields with different meanings.

[0241] 1) The Preferred AP Addresses field carries the address information of the second AP used by the first AP to satisfy the first STA's request. It will be understood that the Preferred AP Addresses field is present in the second response frame only when the Preferred AP List field is set to "1." In this case, the Preferred AP Addresses field contains a MAC address indicating the MAC address of the second AP. It will be understood that each Preferred AP Addresses field in the MAP Parameters Control field corresponds to a different second AP.

[0242] 2) The Preferred AP IDs field exists only when the Preferred AP List field is set to "1" and the Status Code field is equal to SUCCESS. The Preferred AP IDs field is used to carry the ID information of the second AP used by the first AP to satisfy the request of the first STA, such as the AID / USID. The AID / USID can be a 12-bit ID negotiated between APs or generated based on the AP's MAC address. This application does not limit the method for obtaining the AID / USID. It only needs to be obtained through existing technologies and can indicate the corresponding AP. It should be noted that the AID / USID in the same MAP Parameters Control field should indicate the same second AP as the MAC address in the Preferred AP Addresses field.

[0243] (5) The Sensing Responder Addresses field carries the address information of the Sensing Responder selected by the first AP to satisfy the request of the first STA. It is understood that the Sensing Responder Addresses field appears only when the Co-Sensing Initiator field is set to "1" and the Preferred Responder List field is set to "1". In this case, the Sensing Responder Addresses field contains one or more MAC addresses that indicate the Sensing Responder selected by the first AP to satisfy the request of the first STA.

[0244] (6) The Sensing Responder IDs field exists only when the Co-Sensing Initiator field is set to "1", the Preferred Responder List field is set to "1", and the Status Code field is equal to SUCCESS. The Sensing Responder IDs field is used to carry the ID information of the Sensing Responder used by the first AP to satisfy the request of the first STA, such as the AID / USID. The order of the AID / USID should be the same as the order of the MAC addresses in the Sensing Responder Addresses field.

[0245] It should be noted that in scenario 2, the time window for multi-AP joint perception allocated by the first AP in the first request frame should be the same as the multi-AP joint perception time window information carried in the second response frame replied by the first AP to the first STA. For example, the multi-AP joint perception time window information can be carried in the RSTA Availability Window element field in the second response frame shown in Figure 13.

[0246] It can be understood that in scenario 1, S601 and S602 can be referred to as the multi-AP joint perception establishment phase in this scenario, and in scenario 2, S601 to S604 can be referred to as the multi-AP joint perception establishment phase in this scenario. The following examples illustrate the frame interaction process of the multi-AP joint perception establishment phase in the two scenarios with reference to the accompanying drawings.

[0247] Figure 14 is a schematic diagram of the multi-AP joint sensing process corresponding to scenario 1. Figure 14 includes the multi-AP joint sensing establishment phase, the multi-AP joint sensing measurement phase, and the multi-AP joint sensing report feedback phase of scenario 1. Among them, AP1 can be regarded as the first AP, and AP2 and AP3 can be regarded as APs among N APs. In this scenario, AP1, as a Co-Sensing Initiator, sends a Co-Sensing Request frame (i.e., an example of the first request frame) to AP2 to initiate a multi-AP joint perception request. AP2, as a Co-Sensing Responder, sends a Co-Sensing Response frame (i.e., an example of the first response frame) to AP1 to indicate that it accepts the multi-AP joint perception request initiated by AP1. After that, AP1, as a Co-Sensing Initiator, continues to send a Co-Sensing Request frame (i.e., an example of the first request frame) to AP3 to initiate a multi-AP joint perception request. AP3, as a Co-Sensing Responder, sends a Co-Sensing Response frame (i.e., an example of the first response frame) to AP1 to indicate that it receives the multi-AP joint perception request initiated by AP1. Finally, AP1, AP2, and AP3 respectively send SensingMeasurementRequest frames to their associated STA1, STA2, and STA3 to establish a perception session in preparation for the subsequent multi-AP perception measurement. STA1, STA2, and STA3 respectively send SensingMeasurementResponse frames to AP1, AP2, and AP3 to indicate that the perception session establishment is complete. Afterwards, the APs participating in multi-AP joint perception can continue to complete corresponding frame interactions in the multi-AP joint perception measurement phase and the multi-AP joint perception report feedback phase. The specific processes of these two phases will be described in detail in S605 to S607 and will not be described here.

[0248] Figure 15 is a schematic diagram of the multi-AP joint sensing process for scenario 2. Figure 15 includes the multi-AP joint sensing establishment phase, the multi-AP joint sensing measurement phase, and the multi-AP joint sensing report feedback phase for scenario 2. ST4 can be considered the first STA, AP1 can be considered the first AP, and AP2 and AP3 can be considered APs among N APs. The multi-AP joint sensing measurement phase and the multi-AP joint sensing report feedback phase will be described in detail in S605 to S607 and will not be described here. In this scenario, STA4 sends a Co-SBP Request frame (i.e., an example of the second request frame) to AP1 as Co-SBP Initiator to initiate a multi-AP joint perception request, and AP1 sends a Co-SBP Response frame (i.e., an example of the second response frame) to STA4 as Co-SBP Responder to indicate that it accepts the multi-AP joint perception request initiated by STA4. Then, AP1 sends a Co-Sensing Request frame (i.e., an example of the first request frame) to AP2 as Co-Sensing Initiator to initiate a multi-AP joint perception request, and AP2 sends a Co-Sensing Response frame (i.e., an example of the first response frame) to AP1 as Co-Sensing Responder to indicate that it accepts the multi-AP joint perception request initiated by AP1. After that, AP1 continues to send a Co-Sensing Request frame (i.e., an example of the first request frame) to AP3 as Co-Sensing Initiator to initiate a multi-AP joint perception request, and AP3 sends a Co-Sensing Responder to AP1. The Response frame (i.e., an example of the first response frame) indicates the reception of the multi-AP joint perception request initiated by AP1. Finally, AP1, AP2, and AP3 send SensingMeasurementRequest frames to their associated STA1, STA2, and STA3 respectively to establish a perception session. STA1, STA2, and STA3 send SensingMeasurementResponse frames to AP1, AP2, and AP3 respectively to indicate that the perception session establishment is complete. After that, the APs participating in multi-AP joint perception can continue to complete the corresponding frame exchanges in the multi-AP joint perception measurement phase and the multi-AP joint perception report feedback phase. The specific process of the multi-AP joint perception measurement phase will be described in detail in S605, and the specific process of the multi-AP joint perception report feedback phase will be described in detail in S605 to S608, which will not be described here.

[0249] Optionally, after the N APs successfully establish awareness sessions with the associated STAs, the method further includes:

[0250] S605: The first AP triggers N APs to perform multi-AP joint sensing measurement. Two implementation methods of the first AP triggering N APs to perform sensing measurement are given below.

[0251] In implementation method 1, the first AP can sequentially trigger N APs to perform perception measurements. For example, if the second AP among the N APs is not the last AP among the N APs to be triggered to perform perception measurements, the first AP triggers the N APs to perform multi-AP joint perception measurements, including: the first AP determines that the second AP has completed the perception measurement; the first AP sends a first inquiry trigger frame to a third AP among the N APs, the first inquiry trigger frame being used to trigger the third AP to perform perception measurements, the third AP being any AP among the N APs that has not yet been triggered to perform perception measurements; and the first AP receives a first inquiry response frame from the third AP. Optionally, the ninth information in the first inquiry trigger frame is used to trigger the AP that receives the first inquiry trigger frame to perform multi-AP joint perception measurements.

[0252] Optionally, the first inquiry trigger frame includes tenth information, and the tenth information instructs the third AP to start performing perception measurement.

[0253] An example is given to illustrate how the first AP in this implementation method determines that a certain AP among N APs (taking the third AP as an example) completes the perception measurement. Example 1: The first inquiry trigger frame includes information #1. Information #1 includes the duration for the third AP to perform the perception measurement. When the first AP allocates a duration for the third AP, the third AP needs to complete the perception measurement within the allocated duration. After the duration allocated to the third AP expires, the first AP continues to trigger the next AP to perform the perception measurement. Example 2: The first inquiry trigger frame does not include the duration for the third AP to perform the perception measurement. After the first AP triggers the third AP to perform the perception measurement, the third AP can complete the perception measurement with the corresponding STA. The first AP will continue to monitor the channel. When the channel is idle, the first AP believes that the third AP has completed the perception measurement and continues to trigger the next AP to perform the perception measurement.

[0254] In a second implementation, the first AP may assign a perception measurement start time and duration for each of the N APs, and the N APs may perform perception measurements based on their own perception measurement start time and duration. For example, the first AP triggers the N APs to perform multi-AP joint perception measurements, including: the first AP sends a second query trigger frame to the N APs, the second query trigger frame being used to trigger the N APs to perform perception measurements based on their respective corresponding perception measurement start times and durations; and the first AP receives second query response frames from the N APs, the second query response frames instructing the APs to confirm that the perception measurements will be performed based on the corresponding perception measurement start times and durations.

[0255] Optionally, the second inquiry trigger frame includes eighth information, and the eighth information includes the start time and duration of the perception measurement performed by the N APs.

[0256] Optionally, the eleventh information in the second inquiry trigger frame is used to trigger N APs to perform multi-AP joint perception measurement.

[0257] Optionally, the second inquiry trigger frame includes twelfth information, where the twelfth information instructs the N APs to perform perception measurement based on their respective corresponding perception measurement start times and durations.

[0258] The current SBP does not support SBP initiator control over the sensing process. Even if the first AP can initiate a multi-AP joint request, there is no guarantee that multiple sensing results can be used in combination. However, based on the method described in S605, the first AP can control the sensing measurements of multiple APs, allowing them to complete sensing of the target within a shorter period of time. In this case, the sensing results of each AP can be considered soft-synchronized, ensuring that multiple sensing results can be used in combination. Therefore, if the first AP's sensing results are unavailable due to interference or weak signal strength at the BSS edge, the "simultaneous" sensing results of N APs can be used, thus avoiding sensing task failure.

[0259] For example, the query trigger frame for triggering multi-AP joint perception, such as the first query trigger frame or the second query trigger frame, may be referred to as a Co-SBP Polling Trigger frame in this application.

[0260] The above-mentioned implementation method 1 and implementation method 2 are illustrated below with reference to FIG16 and FIG17 .

[0261] Figure 16 is a schematic diagram of multiple APs performing joint sensing based on Implementation Method 1. AP1 can be considered the first AP, and AP2 and AP3 can be considered APs among the N APs. As shown in Figure 16, AP1 first performs sensing measurements. After completing the sensing measurements, AP1 sends a Co-SBP Polling Trigger frame to AP2, triggering AP2 to perform sensing measurements. AP2 responds with a CTS-to-self frame to AP1. AP2 then begins sensing measurements. After AP1 determines that AP2 has completed the sensing measurements, it sends a Co-SBP Polling Trigger frame to AP3, triggering AP3 to perform sensing measurements. AP3 responds with a CTS-to-self frame to AP1. AP3 then begins sensing measurements. This continues until all APs participating in the multi-AP sensing measurement complete sensing measurements based on the Co-SBP Polling Trigger frame sent by AP1.

[0262] Figure 17 is a schematic diagram of multiple APs performing joint sensing based on Implementation Method 2. AP1 can be considered the first AP, and AP2 and AP3 can be considered APs among the N APs. As shown in Figure 17, AP1 sends a Co-SBP Polling Trigger frame to AP2 and AP3 to trigger AP2 and AP3 to perform sensing measurements. The Co-SBP Polling Trigger frame includes the start time and duration of AP2's sensing measurement and the start time and duration of AP3's sensing measurement. AP2 and AP3 then send CTS-to-self frames to AP1 in response. AP1, AP2, and AP3 then perform sensing measurements in sequence based on their respective sensing measurement start times and durations.

[0263] Figure 18 is a schematic diagram of the frame structure of a possible inquiry trigger frame (hereinafter referred to as a Co-SBP Polling Trigger frame) for triggering multi-AP joint perception proposed by this application. The inquiry trigger frame for triggering multi-AP joint perception can be regarded as a Polling Trigger frame for multi-AP joint perception redesigned on the basis of the existing Trigger frame. The existing Trigger frame cannot support the function of triggering perception measurements of multiple APs at the same time as this application, while the inquiry trigger frame shown in Figure 18 can support the scenario of multi-AP joint perception of this application. This application only makes modifications to the trigger-based common information (Trigger Dependent Comment Info) field and the User Info field in the common information (Common Info) field of the existing Trigger frame.

[0264] As shown in Figure 18, the Co-SBP Polling Trigger frame includes fields such as the Common Info field and the User Info List field. The Common Info field contains common information that all STAs associated with the AP need to read, while the User Info List field contains multiple User Info fields, each of which corresponds to information that a STA needs to read. The following describes some fields in the Co-SBP Polling Trigger frame that are relevant to this application.

[0265] (1) The Co-SBP Polling Trigger frame adds a new frame type to the existing trigger frame, indicating that the Co-SBP Polling Trigger frame is an inquiry trigger frame used to trigger multi-AP joint perception. Exemplarily, the present application extends a frame type in the Sensing Trigger Subtype field of the Trigger Dependent Common Info field of the Common Info field of the existing trigger frame to indicate that the trigger frame is a Co-SBP Polling Trigger frame. Exemplarily, as shown in Table 3, when the value of the Sensing Trigger Subtype field is 5 (i.e., an example of the ninth information or an example of the eleventh information), it indicates that the current trigger frame is a Co-SBP Polling Trigger frame, and the AP that receives this frame needs to return a CTS-to-self frame in response.

[0266] Table 3

[0267] (2) The Trigger Dependent User Info field in the User Info List field of the Co-SBP Polling Trigger frame, which is based on the trigger frame type, is used to carry parameters required for sensing measurements assigned to different APs. This parameter includes the eighth information. Exemplarily, when the value of the Sensing Trigger Subtype field in the trigger frame is 5, the trigger frame is considered to be a Co-SBP Polling Trigger frame, and the User Info List field of the Co-SBP Polling Trigger frame carries the Trigger Dependent User Info field. For example, Figure 19 is a schematic diagram of the structure of the User Info List field, where the User Info List field includes multiple User Info fields, each User Info field includes an AID12 field and a Trigger Dependent User Info field. The AID12 field represents an association identifier of an AP, and the Trigger Dependent User Info field indicates the number of HE-LTF repetitions of the NDP frame sent by the AP indicated by the AID12 field in the Sounding Phase, as well as the start time and duration of the perception measurement of the AP indicated by the AID12 field.

[0268] As shown in Figure 19, the Trigger Dependent User Info field includes the Co-SBP repetition count (Co-SBP Rep) field, the start time (Start Time) field, and the duration (Duration) field. The following describes in detail the meaning of each field in the Trigger Dependent User Info field and the specific parameters it carries.

[0269] The Co-SBP Rep field is used to indicate the number of HE-LTF repetitions of the NDP frame sent by the AP corresponding to AID12 in the Sounding Phase.

[0270] The Start Time field is used to indicate a first duration, which is used to determine the expected start time of the perception measurement for the AP corresponding to AID 12. For example, the expected start time may be the time corresponding to the first duration after the Co-SBP Polling Trigger frame is received.

[0271] The Duration field indicates the duration of the sounding for the AP corresponding to AID 12. If configured, each AP should complete the sounding within this duration. Duration can be a specified duration in units of 32 μs. For example, if the value of this field in the corresponding Co-SBP Polling Trigger frame in Implementation Method 1 is set to all zeros.

[0272] Optionally, the AP that receives the Co-SBP Polling Trigger frame can determine whether to perform perception measurements based on implementation method one or implementation method two based on the number of User Info fields carried in the Co-SBP Polling Trigger frame. Specifically, if it is implementation method one, the Co-SBP Polling Trigger frame carries only one User Info field (i.e., the User Info of the triggered AP); if it is implementation method two, the Co-SBP Polling Trigger frame carries multiple User Info fields (i.e., the User Info of all triggered APs); therefore, the AP can determine whether to perform subsequent perception measurements based on implementation method one or implementation method two based on the number of User Info fields contained in the Co-SBP Polling Trigger frame.

[0273] Optionally, the Trigger Dependent User Info field may further include a type (Model) field, which is used to indicate whether the AP corresponding to AID12 performs perception measurement based on implementation method 1 or implementation method 2. For example, this field is indicated by 1 bit. When the value of this field is 0, it indicates that the AP starts perception measurement (i.e., implementation method 1). When the value of this field is 1, it indicates that the AP performs perception measurement based on the corresponding perception measurement start time and duration (i.e., implementation method 2).

[0274] For example, if AP#1 among N APs determines to perform measurement based on implementation method 1 based on the first query trigger frame, AP#1 may not read the Start Time field in the first query trigger frame. If AP#1 determines to perform measurement based on implementation method 2 based on the second query trigger frame, AP#1 needs to read the values ​​of the Start Time field and the Duration field of the User Info field containing its own AID in the second query trigger frame.

[0275] For example, when the first AP triggers AP#1 to perform measurements based on implementation method one through inquiry trigger frame #1, and the first AP does not indicate the duration of perception measurement to AP#1, the Duration field in the first trigger frame can be set to all 0s.

[0276] It can be understood that S605 in this application can be referred to as a multi-AP joint sensing stage.

[0277] Optionally, after the N APs complete sensing measurements, if the multi-AP joint sensing scenario is scenario one, the method further includes S606 and S607; if the multi-AP joint sensing scenario is scenario two, the method further includes S606 to S608:

[0278] S606: The first AP sends a first report trigger frame to N APs, where the first report trigger frame is used to trigger the N APs to report measurement results of multi-AP joint perception.

[0279] Optionally, the thirteenth information in the first report trigger frame is used to trigger the AP that receives the first report trigger frame to report the measurement result of multi-AP joint perception.

[0280] Optionally, the first report trigger frame includes type information of the perception measurement result, where the type information includes one or more types in the first request frame, and the N APs report corresponding measurement results based on the type information.

[0281] For example, the first report trigger frame in the present application may be referred to as a Co-SBP Report Trigger frame.

[0282] Optionally, the Co-SBP Report Trigger frame can reuse the existing Sensing Report Trigger frame. It is only necessary to add a new trigger frame type in the Sensing Report Trigger frame to indicate that the Co-SBP Report Trigger frame is a trigger frame used to trigger the reporting of joint sensing results of multiple APs, and at the same time indicate that the AP receiving this frame needs to return an SBP report frame uplink at the same time after a SIFS time interval. Exemplarily, the present application extends a frame type in the Sensing Trigger Subtype field of the Trigger Dependent Comment Info field of the Common Info field of the existing Sensing Report Trigger frame to indicate that the trigger frame is a Co-SBP Report Trigger frame. For example, as shown in Table 3, when the value of the Sensing Trigger Subtype field is 6 (i.e., an example of the thirteenth information), it indicates that the current trigger frame is a Co-SBP Report Trigger frame.

[0283] S607: The N APs respectively send measurement results to the first AP. Correspondingly, the first AP receives the measurement results from the N APs.

[0284] S608: The first AP sends measurement results of N APs to the first STA. Correspondingly, the first STA receives the perception measurement results of the N APs from the first AP.

[0285] It can be understood that S605 to S608 in this application can be referred to as a multi-AP joint perception report feedback stage.

[0286] It should be understood that the size of the serial numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0287] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0288] It should also be understood that in some of the above embodiments, devices in existing network architectures are mainly used as examples for illustrative purposes, and it should be understood that the embodiments of the present application do not limit the specific form of the devices. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.

[0289] It can be understood that in the above-mentioned method embodiments, the methods and operations implemented by the device (such as the Co-Sensing responder, Co-Sensing initiator, etc.) can also be implemented by components of the device (such as chips or circuits).

[0290] The above is a detailed description of the method provided by the embodiment of the present application in conjunction with Figures 1 to 19. The above method is mainly introduced from the perspective of the interaction between the Co-Sensing initiator and the Co-Sensing responder. It can be understood that the Co-Sensing initiator and the Co-Sensing responder, in order to implement the above functions, include hardware structures and / or software modules corresponding to the execution of each function.

[0291] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0292] Hereinafter, the communication device provided by the embodiment of the present application will be described in detail with reference to Figures 20 and 21. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for the content not described in detail, please refer to the above method embodiment. For the sake of brevity, some contents will not be repeated. In the embodiment of the present application, the functional modules of the Co-Sensing initiator or the Co-Sensing responder can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.

[0293] The above describes in detail the method for data transmission provided by the present application. The following describes the communication device provided by the present application. In one possible implementation, the device is used to implement the steps or processes corresponding to the Co-Sensing responder in the above method embodiment. In another possible implementation, the device is used to implement the steps or processes corresponding to the Co-Sensing initiator in the above method embodiment.

[0294] Figure 20 is a schematic block diagram of a communication device 200 provided in an embodiment of the present application. As shown in Figure 20 , the device 200 may include a communication unit 210 and a processing unit 220. The communication unit 210 can communicate with the outside world, and the processing unit 220 is used to process data. The communication unit 210 may also be referred to as a communication interface or a transceiver unit.

[0295] In one possible design, the device 200 can implement steps or processes corresponding to those performed by the Co-Sensing initiator in the above method embodiment, wherein the processing unit 220 is used to perform processing-related operations of the Co-Sensing initiator in the above method embodiment, and the communication unit 210 is used to perform sending-related operations of the Co-Sensing initiator in the above method embodiment.

[0296] In another possible design, the device 200 may implement steps or processes corresponding to those performed by the Co-Sensing responder in the above method embodiment, wherein the communication unit 210 is used to perform reception-related operations of the Co-Sensing responder in the above method embodiment, and the processing unit 220 is used to perform processing-related operations of the Co-Sensing responder in the above method embodiment.

[0297] It should be understood that the device 200 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 200 can be specifically the Co-Sensing initiator in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the Co-Sensing initiator in the above-mentioned method embodiment, or the device 200 can be specifically the Co-Sensing responder in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the Co-Sensing responder in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

[0298] The apparatus 200 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the Co-Sensing initiator in the above-mentioned method, or the apparatus 200 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the Co-Sensing responder in the above-mentioned method. The functions can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the communication unit can be replaced by a transceiver (for example, the sending unit in the communication unit can be replaced by a transmitter, and the receiving unit in the communication unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0299] In addition, the above-mentioned communication unit can also be a transceiver circuit (for example, it can include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit. In an embodiment of the present application, the device in Figure 20 can be the Co-Sensing responder or Co-Sensing initiator in the aforementioned embodiment, or it can be a chip or chip system, such as: system on chip (SoC). Among them, the communication unit can be an input and output circuit, a communication interface; the processing unit is a processor or microprocessor or integrated circuit integrated on the chip. This is not limited here.

[0300] Figure 21 is a schematic block diagram of a communication device 300 provided in an embodiment of the present application. The device 300 includes a processor 310 and a transceiver 320. The processor 310 and the transceiver 320 communicate with each other via an internal connection path. The processor 310 is configured to execute instructions to control the transceiver 320 to transmit and / or receive signals.

[0301] Optionally, the device 300 may further include a memory 330, which communicates with the processor 310 and the transceiver 320 via an internal connection path. The memory 330 is used to store instructions, and the processor 310 can execute the instructions stored in the memory 330. In one possible implementation, the device 300 is used to implement the various processes and steps corresponding to the Co-Sensing initiator in the above method embodiment. In another possible implementation, the device 300 is used to implement the various processes and steps corresponding to the Co-Sensing responder in the above method embodiment.

[0302] It should be understood that the device 300 can be specifically the Co-Sensing initiator or Co-Sensing responder in the above-mentioned embodiment, or it can be a chip or a chip system. Correspondingly, the transceiver 320 can be the transceiver circuit of the chip, which is not limited here. Specifically, the device 300 can be used to execute the various steps and / or processes corresponding to the Co-Sensing initiator or Co-Sensing responder in the above-mentioned method embodiment. Optionally, the memory 330 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 310 can be used to execute instructions stored in the memory, and when the processor 310 executes instructions stored in the memory, the processor 310 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the Co-Sensing initiator or Co-Sensing responder.

[0303] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0304] It should be noted that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, digital signal processing (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The processor in the embodiments of the present application can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

[0305] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0306] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0307] In addition, the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the operations and / or processes performed by the Co-Sensing initiator or the Co-Sensing responder in each method embodiment of the present application are executed.

[0308] The present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processes performed by the Co-Sensing initiator or the Co-Sensing responder in the various method embodiments of the present application are executed.

[0309] In addition, the present application further provides a chip, the chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is configured to execute the computer program stored in the memory, so that the operations and / or processing performed by the Co-Sensing initiator or the Co-Sensing responder in any method embodiment are performed.

[0310] Furthermore, the chip may further include a communication interface. The communication interface may be an input / output interface, or an interface circuit, etc. Furthermore, the chip may further include a memory.

[0311] In addition, the present application also provides a communication system, including the Co-Sensing initiator and the Co-Sensing responder in the embodiments of the present application.

[0312] It should also be noted that the memory described herein is intended to comprise, but not be limited to, these and any other suitable types of memory.

[0313] Those skilled in the art will appreciate that the various exemplary units and algorithmic steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented using hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for ease of description and brevity, the specific operating processes of the systems, devices, and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units described is merely a logical functional division. In actual implementation, other divisions may be used, such as multiple units or components being combined or integrated into another system, or some features being omitted or not implemented. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interface, or indirect coupling or communication connection between devices or units, which may be electrical, mechanical, or other forms. The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0314] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0315] It should be understood that references to "embodiments" throughout this specification mean that a particular feature, structure, or characteristic associated with the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0316] It should also be understood that the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of multiple objects.

[0317] It should also be understood that in this application, "when", "if" and "if" all mean that the network element will make corresponding processing under certain objective circumstances, which is not a time limit, and does not require the network element to make judgment actions when implementing it, nor does it mean that there are other limitations.

[0318] It should also be understood that, in this application, "at least one" means one or more, and "plurality" means two or more. "At least one item" or similar expressions refers to one or more items, that is, any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a, b, and c.

[0319] It should also be understood that expressions similar to "the item includes one or more of the following: A, B, and C" in this application generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C. The above example uses A, B, and C as an example to illustrate the optional items of the item. When the expression is "the item includes at least one of the following: A, B, ..., and X", that is, when the expression contains more elements, the items applicable to the item can also be obtained according to the above rules.

[0320] It should also be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A alone, including A and B, and B alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects are in an "or" relationship. For example, "A / B" means: A or B.

[0321] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, and B can also be determined based on A and / or other information.

[0322] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method of sensing, characterized in that: include: The first access point AP sends first request frames corresponding to the N APs to the N APs respectively, where the first request frame is used for the AP to initiate a multi-AP joint proxy perception request, where N is a positive integer; The first AP receives first response frames from the N APs respectively, where the first response frames are used to indicate acceptance of a multi-AP joint proxy perception request.

2. The method according to claim 1, characterized in that The first request frame includes first information, wherein the first information indicates that the first request frame is a request frame for AP to initiate multi-AP joint proxy perception, and the first information is carried in the first request frame including a public function / protected dual public function Public Action / Protected Dual of Public Action field.

3. The method according to claim 1 or 2, characterized in that: The first request frame includes second information, where the second information includes parameters required for a second AP to perform multi-AP joint proxy perception, and the second AP is an AP that receives the first request frame.

4. The method according to claim 3, characterized in that: The parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

5. The method according to any one of claims 1 to 4, characterized in that The first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first AP receives a second request frame from the first station STA, where the second request frame is used by the STA to initiate a multi-AP joint proxy perception request; The first AP sends a second response frame to the first STA, where the second response frame indicates acceptance of the multi-AP joint proxy awareness request.

7. The method according to claim 6, characterized in that The second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the public function / protected dual public function Public Action / Protected Dual of Public Action field included in the second request frame.

8. The method according to claim 6 or 7, characterized in that: The second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

9. The method according to claim 8, characterized in that The parameters required for the multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the required number of APs is required, whether the AP receiving the second request frame needs to perform perception measurement, the required number of perception response STAs, the number of perception response STAs is required, whether the AP receiving the second request frame is recommended for joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

10. The method according to claim 9, characterized in that When the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, and the sixth information includes the perception parameter allocated to each of the recommended APs.

11. The method according to claim 10, characterized in that The sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for sensing, the number of required sensing response STAs, whether the number of sensing response STAs is mandatory, and a trigger-based detection phase type.

12. The method according to any one of claims 6 to 11, characterized in that The second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by a STA, and the seventh information is carried in the second response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: The first AP triggers the N APs to perform multi-AP joint perception measurement.

14. The method according to claim 13, characterized in that If a second AP among the N APs is not the last AP among the N APs to be triggered to perform perception measurement, the first AP triggers the N APs to perform multi-AP joint perception measurement, including: The first AP determines that the second AP completes the sensing measurement; The first AP sends a first inquiry trigger frame to a third AP among the N APs, where the first inquiry trigger frame is used to trigger the third AP to perform perception measurement, and the third AP is any AP among the N APs that has not been triggered to perform perception measurement; The first AP receives a first inquiry response frame from the third AP.

15. The method according to claim 13, characterized in that The first AP triggers the N APs to perform multi-AP joint perception measurement, including: The first AP sends a second inquiry trigger frame to the N APs, where the second inquiry trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration; The first AP receives second inquiry response frames from the N APs, where the second inquiry response frames indicate that the AP confirms to perform perception measurement based on the corresponding perception measurement start time and duration.

16. The method according to claim 15, characterized in that The second inquiry trigger frame includes eighth information, and the eighth information includes the start time and duration of the perception measurement performed by the N APs.

17. The method according to claim 14, characterized in that The ninth information in the first inquiry trigger frame is used to trigger the AP receiving the first inquiry trigger frame to perform multi-AP joint perception measurement, and the ninth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first inquiry trigger frame.

18. The method according to claim 14 or 17, characterized in that The first inquiry trigger frame includes tenth information, and the tenth information instructs the third AP to start performing perception measurement.

19. The method according to claim 15 or 16, characterized in that The eleventh information in the second inquiry trigger frame is used to trigger the N APs to perform multi-AP joint perception measurement, and the eleventh information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

20. The method according to any one of claims 15, 16 and 19, characterized in that: The second inquiry trigger frame includes twelfth information, where the twelfth information instructs the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration.

21. The method according to any one of claims 6 to 20, characterized in that The method further comprises: The first AP sends a first report trigger frame to the N APs, where the first report trigger frame is used to trigger the N APs to report measurement results of multi-AP joint perception; The first AP receives measurement results from the N APs.

22. The method according to claim 21, characterized in that The method further comprises: The first AP sends the measurement results of the N APs to the first STA.

23. The method according to claim 21 or 22, characterized in that The thirteenth information in the first report trigger frame is used to trigger the AP receiving the first report trigger frame to report the measurement results of multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

24. A method of sensing, characterized in that include: The second access point AP receives a first request frame from the first AP, where the first request frame is used for the AP to initiate a multi-AP joint proxy perception request, and the second AP is any AP among the N APs for which the first AP requests multi-AP joint proxy perception, where N is an integer; The second AP sends a first response frame to the first AP, where the first response frame is used to indicate acceptance of the multi-AP joint proxy perception request.

25. The method according to claim 24, characterized in that The first request frame includes first information, wherein the first information indicates that the first request frame is a request frame for AP to initiate multi-AP joint proxy perception, and the first information is carried in the first request frame including a public function / protected dual public function Public Action / Protected Dual of Public Action field.

26. The method according to claim 24 or 25, characterized in that The first request frame includes second information, and the second information includes parameters required for the second AP to perform multi-AP joint proxy perception.

27. The method according to claim 26, characterized in that The parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

28. The method according to any one of claims 24 to 27, characterized in that The first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

29. The method according to any one of claims 24 to 28, characterized in that The method further comprises: The second AP performs multi-AP joint perception measurement under the triggering of the first AP.

30. The method according to claim 29, characterized in that The second AP performs multi-AP joint sensing measurement under the triggering of the first AP, including: The second AP receives a third inquiry trigger frame from the first AP, where the third inquiry trigger frame is used to trigger the second AP to perform perception measurement; The second AP sends a third inquiry response frame to the first AP.

31. The method according to claim 29, characterized in that The first AP triggers the N APs to perform multi-AP joint perception measurement, including: The second AP receives a second inquiry trigger frame from the first AP, where the second inquiry trigger frame is used to trigger the N APs to perform perception measurements based on their respective corresponding perception measurement start time and duration; The second AP sends a second inquiry response frame to the first AP, where the second inquiry response frame indicates that the second AP confirms to perform the perception measurement based on the corresponding perception measurement start time and duration.

32. The method according to claim 31, characterized in that The second inquiry trigger frame includes eighth information, and the eighth information includes the start time and duration of the perception measurement performed by the N APs.

33. The method according to claim 30, characterized in that The fourteenth information in the third inquiry trigger frame is used to trigger the second AP to perform multi-AP joint perception measurement, and the fourteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the first inquiry trigger frame.

34. The method according to claim 30 or 33, characterized in that The third inquiry trigger frame includes fifteenth information, and the fifteenth information instructs the second AP to start performing perception measurement.

35. The method according to claim 31 or 32, characterized in that The eleventh information in the second inquiry trigger frame is used to trigger the N APs to perform multi-AP joint perception measurement, and the eleventh information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

36. The method according to any one of claims 31, 32 and 35, characterized in that: The second inquiry trigger frame includes twelfth information, and the twelfth information indicates that the AP receiving the second inquiry trigger frame performs perception measurement based on the corresponding perception measurement start time and duration.

37. The method according to any one of claims 24 to 36, characterized in that The method further comprises: The second AP receives a first report trigger frame from the first AP, where the first report trigger frame is used to trigger the second AP to report a measurement result of multi-AP joint perception; The second AP sends the measurement result to the first AP.

38. The method according to claim 37, characterized in that The thirteenth information in the first report trigger frame is used to trigger the reception of the second AP to report the measurement result of the multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

39. A method of sensing, characterized in that include: The first station STA sends a second request frame to the first access point AP, where the second request frame is used by the STA to initiate a multi-AP joint proxy perception request; The first STA receives a second response frame from the first AP, where the second response frame indicates acceptance of the multi-AP joint proxy awareness request.

40. The method according to claim 39, characterized in that The second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the public function / protected dual public function Public Action / Protected Dual of Public Action field included in the second request frame.

41. The method according to claim 39 or 40, characterized in that The second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

42. The method according to claim 41, characterized in that The parameters required for the multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the required number of APs is required, whether the AP receiving the second request frame needs to perform perception measurement, the required number of perception response STAs, the number of perception response STAs is required, whether the AP receiving the second request frame is recommended for joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

43. The method according to claim 42, characterized in that When the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, and the sixth information includes the perception parameter allocated to each of the recommended APs.

44. The method according to claim 43, characterized in that The sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for sensing, the number of required sensing response STAs, whether the number of sensing response STAs is mandatory, and a trigger-based detection phase type.

45. The method according to any one of claims 39 to 44, characterized in that The second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by a STA, and the seventh information is carried in the second response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

46. ​​The method according to any one of claims 39 to 45, characterized in that The method further comprises: The first STA receives a measurement result of multi-AP joint perception from the first AP.

47. A communication device, characterized in that: A method comprising a module or unit for executing any one of claims 1 to 23, or a module or unit for executing any one of claims 24 to 38, or a module or unit for executing any one of claims 39 to 46.

48. A communication device, characterized in that: The device comprises at least one processor and a communication interface, wherein the communication interface is used to input and / or output signals, and the at least one processor is used to execute a computer program stored in a memory so that the communication device implements the method as described in any one of claims 1 to 23, or implements the method as described in any one of claims 24 to 38, or implements the method as described in any one of claims 39 to 46.

49. A processing device, characterized in that The device comprises a processor configured to execute a computer program stored in a memory so that the device implements the method according to any one of claims 1 to 23, or implements the method according to any one of claims 24 to 38, or implements the method according to any one of claims 39 to 46.

50. A processing device, characterized in that include: Memory for storing computer programs; A processor, configured to call and run the computer program from the memory so that the apparatus implements the method as claimed in any one of claims 1 to 23, or implements the method as claimed in any one of claims 24 to 38, or implements the method as claimed in any one of claims 39 to 46.

51. A computer readable medium, characterized in that The method comprises a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 38, or the method according to any one of claims 39 to 46.

52. A computer program product, comprising a computer program, which, when executed on a computer, enables the computer to execute the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 38, or the method according to any one of claims 39 to 46.

Images